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.
git 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/agent-scope)<a href="https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/agent-scope"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/agent-scope/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ibrain-bvba/gutt-claude-code-plugin/agent-scope"><img src="https://agentmods.dev/badge/commands/ibrain-bvba/gutt-claude-code-plugin/agent-scope.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00071 | $0.01045 |
| Opus 5.5 | $0.00028 | $0.00418 |
| Sonnet 5.5 | $0.00014 | $0.00209 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
agent-scope scanned grade A with 0 findings 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gutt agent scope
The read or change for this invocation has already been applied, deterministically, by the plugin's UserPromptSubmit hook. It reports the outcome as context alongside this message.
Read the outcome and take exactly one of the three branches below, in this order.
1. No outcome accompanies this message
Then whether anything was applied is unknown — not "nothing happened". The write and
the report are separate steps, so a missing report does not mean a missing write. Say
that, tell the user to run /gutt-pro:agent-scope show before retrying, and stop. Do not
re-run the command and do not guess.
2. The outcome contains the phrase no argument given
Only then, help the user choose one. Check this before branch 3 — an outcome with no argument also reports what is in force, so testing for that first would swallow this case.
- Find the labels already in use, so a team converges on one instead of each person
inventing their own. Search the graph for existing named workflow identities and collect the
part after
--in the names you find. Read-only — register nothing, write nothing. Search registered names; if what comes back is node IDs, the--has been collapsed to a single-and the label cannot be split out reliably — say the survey was inconclusive rather than guessing where a name ends. - Check what the candidate would collide with. A registered name is permanent: registration merges on name and group, so reusing a label that belongs to another context silently joins that context's memory to this one, and it cannot be undone or separated afterwards. If a label you are about to suggest already has workflows whose work is plainly someone else's, say so and steer away from it.
- Ask, using AskUserQuestion — the scope type and the name. Offer the labels from step 1 as options where any exist, and say what each already appears to cover. A team label is the one to prefer when several directories are genuinely one product; a project label when this one should keep its own memory.
- Tell the user the exact line to type. You cannot apply it yourself — this command's effect comes from the hook that sees the typed prompt, and a command you invoke never reaches that hook. End with the line, filling in the type and name that were actually chosen, and nothing after it:
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.
- 1mo ago Changed · +12 tokens per session 8e17638ef3bd
- 1mo ago First seen · 82 lines · 59 tokens per session scan A 8ef44737e3b6
agent-scope is a command published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,045 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.