Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/ibrain-bvba/gutt-claude-code-plugin/statuslinegit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/statusline)<a href="https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/statusline"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/statusline.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00058 | $0.00342 |
| Opus 5 | $0.00029 | $0.00171 |
| Sonnet 5 | $0.00012 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade B, and why
statusline scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
/gutt-pro:statusline install the HUD in ~/.claude/settings.json What it actually says
gutt statusline
The setting change for this invocation has already been applied, deterministically, by the plugin's UserPromptSubmit hook. It reports the outcome as context alongside this message.
Report that outcome to the user as a short block, and do nothing else: no tools, no file reads, no re-running the command, no editing settings yourself.
If no such outcome accompanies this message, then nothing was applied — say exactly that and stop.
Forms:
/gutt-pro:statusline install the HUD in ~/.claude/settings.json
/gutt-pro:statusline off remove it again
/gutt-pro:statusline status report whether it is installed
A plugin cannot put a status line in place on its own — Claude Code accepts one only from your own settings file — so this command is the only way the gutt HUD appears, and it never runs unless you type it. The original settings file is backed up before either change.
What it installs points at a stable path rather than at the plugin's versioned directory, so upgrading gutt does not break it. If the HUD disappears on its own, that is Claude Code dropping the key while rewriting settings; the next session puts it back.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 36 lines · 58 tokens per session scan B 31bf8bb48ac5
statusline is a command published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 342 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.