I made Claude Mod roll movie credits after a coding session

Claude Mods looked interesting, but I wanted to understand what you could actually build with them beyond security hooks and telemetry. So I built something deliberately small and slightly ridiculous: Roll Credits . Type /credits at the end of a Claude Code session and it turns the work you just did into movie-style credits inside Claude. You’re the director. Your most-edited file gets the starring role. Other edited files become the supporting cast. Tools Claude used get a special thanks. Failed or denied tool calls become plot twists. The credits actually scroll in a native Claude pane. You can pause them into a still view, replay them, close them, or use /credits --text if you just want the recap. Roll Credits uses Claude's new Mods/function-hook APIs to observe session events and render the credits using Claude's native pane controls. There is no server, no second model call, and no AI-generated summary. Everything comes from local counters collected while the Mod is loaded. Install Mods are still early access, so function hooks need to be enabled. claude plugin marketplace add smukh/roll-credits claude plugin install roll-credits@roll-credits-marketplace CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude Restart Claude after installing, then try: /credits demo That uses clearly labeled fictional data, so you can see the whole thing immediately. For a real session: /credits /credits --still /credits --text /credits The Bug Strikes Back A couple of limitations are intentional. It only counts activity observed while the Mod is loaded, and file credits come from successful Edit , Write , and NotebookEdit calls. Changes made through Bash or another editor are not counted. The numbers describe session activity, not code quality. Everything stays in memory, there is no telemetry, and the project is MIT licensed. Repo + demo + install instructions: github.com/smukh/roll-credits