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/graph-tl/graph/retrogit clone --depth 1 https://github.com/Graph-tl/graphWhat 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.00000 | $0.00224 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
retro 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 yesterday.
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.
What it actually says
The user has identified unwanted agent behavior in this session. Run an ad-hoc retro to capture it.
Steps
-
Identify the behavior — Review what just happened in this conversation. What did the agent do wrong? Common issues: skipping discovery, jumping to implementation without adding to graph, not pausing after tasks, ignoring graph workflow, not checking knowledge first.
-
Root cause — Why did it happen? Missing instruction in CLAUDE.md? Ambiguous rule? Agent prompt gap? Convention not enforced by tooling?
-
Propose a fix — Draft the exact CLAUDE.md instruction or graph knowledge entry that would prevent this in future sessions. Present it to the user for approval.
-
Record it — Based on user approval:
- Add to CLAUDE.md if it's a behavioral rule the default agent should always follow
- Write as graph knowledge if it's project-specific context
- Add as a graph node via
graph_planif it needs tooling changes
-
Confirm — Show the user what was recorded and where.
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.
- yesterday First seen · 17 lines · 0 tokens per session scan A 8521a018d707
retro is a command published in the GitHub repository Graph-tl/graph (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 224 tokens. 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.