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/deploy-checkgit 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.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
deploy-check scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **API health**: `curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://api.gostoa.dev/health` — must be 200 What it actually says
Post-merge CD verification. Run after merging a PR to main.
Check each step and report Go/Fix:
- CI on main:
gh run list --branch main --limit 5 --json status,conclusion,name,headSha— latest must besuccess - API health:
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://api.gostoa.dev/health— must be 200 - Gateway health:
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://mcp.gostoa.dev/health— must be 200 - Console:
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://console.gostoa.dev— must be 200 - Portal:
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://portal.gostoa.dev— must be 200 - Pods:
kubectl get pods -n stoa-system -o wide— all Running, no CrashLoopBackOff - ArgoCD:
kubectl get applications -n argocd -o custom-columns='NAME:.metadata.name,SYNC:.status.sync.status,HEALTH:.status.health.status'— all Synced+Healthy - Images:
kubectl get deployments -n stoa-system -o custom-columns='NAME:.metadata.name,IMAGE:.spec.template.spec.containers[0].image'— verify latest tags
Output a table:
| # | Check | Status | Detail |
|---|
Verdict: Go (all pass) or Fix (any fail + corrective actions).
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 · 20 lines · 0 tokens per session scan A 1f0915d7d3a3
deploy-check 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 397 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.
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.