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/grcengineering/companion/progressgit clone --depth 1 https://github.com/grcengineering/companionWhat 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.00016 | $0.00126 |
| Opus 5 | $0.00008 | $0.00063 |
| Sonnet 5 | $0.00003 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
progress 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 2d 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.
What it actually says
Progress Command
Use when the learner asks what they have learned or what to revisit.
Flow
- List concepts as not yet covered, touched, practised, or internalised.
- Ask one recall question for a touched concept.
- Suggest one next rep.
Boundary
Track learner understanding, not compliance maturity.
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.
- 2d ago First seen · 25 lines · 16 tokens per session scan A 1b03103e54d6
progress is a command published in the GitHub repository grcengineering/companion (32 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 126 once invoked, about $0.0001 per session on Opus 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-30.
Other commands, from other repositories
health
Check FedRAMP MCP server health status.
evidence-examples
Get evidence examples for FedRAMP compliance.
control-requirements
Get all requirements for a NIST control.
list-controls
List NIST controls from FedRAMP FRMR documents.
compare-versions
Compare two versions of an FRMR document.
control-coverage
Analyze NIST control family coverage.