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/stoa-platform/stoa/statusgit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00187 |
| Opus 5 | $0.00000 | $0.00093 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
status 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
Quick project status snapshot.
Gather and display:
- Git: current branch, last 3 commits (
git log --oneline -3), uncommitted changes (git status --short) - PRs: open PRs (
gh pr list --limit 5) - CI: last 5 workflow runs on main (
gh run list --branch main --limit 5) - Pods:
kubectl get pods -n stoa-system --no-headers(skip if kubectl unavailable) - Ops log: last 5 entries from
~/.claude/projects/-Users-torpedo-hlfh-repos-stoa/memory/operations.log - Tokens today: parse
~/.claude/stats-cache.jsonfor today's usage
Format as a compact table. One-liner per section. No commentary.
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 · 13 lines · 0 tokens per session scan A 2fd03a30ff4d
status is a command published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 187 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
speckit.agent-context.update
Proxy for speckit.agent-context.update.md.
speckit.git.remote
Proxy for speckit.git.remote.md.
test-status
Preview which changed files trigger the three-gate rule and may need tests.
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.