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/eddiebelaval/squireWrote 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/eddiebelaval/squire/status)<a href="https://agentmods.dev/commands/eddiebelaval/squire/status"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/status/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/eddiebelaval/squire/status"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/status.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.00000 | $0.00295 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 5d 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
/status - Project Status Report
You are creating a comprehensive status report for a non-technical product manager.
Report Format:
🌿 Git Status
- Current branch
- Uncommitted changes count
- Commits ahead of main
- Last commit message
📦 What's Changed
List changed files organized by category:
- 🎨 UI Components
- ⚙️ Business Logic
- 🗄️ Database/Data
- 📝 Documentation
- ✅ Tests
🚀 Deployment Status
- Can it be deployed? (yes/no)
- Build status (passing/failing)
- Any blockers?
✅ Quality Checks
- Tests: Passing/Failing (count)
- Type errors: None/Count
- Lint issues: None/Count
- Accessibility: ✅/⚠️
📊 Complexity Summary
- Files changed: [count]
- Lines added: [count]
- Lines removed: [count]
- Complexity rating: Simple/Medium/Complex
💡 What This Means
Summarize in 2-3 sentences:
- Where we are in the feature
- What's working
- What's left to do (if anything)
🎯 Next Steps
- Immediate actions needed
- Ready for review? (yes/no)
- Ready to deploy? (yes/no)
Note: Use simple language. Focus on product impact, not technical details.
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.
- 5d ago First seen · 50 lines · 0 tokens per session scan A 45e59b8b339b
status is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 295 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-09-03.
Other commands, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
planning
Planning semanal de equipo con revisión de RFCs, priorización, asignación por responsable/pareja/squad y seguimiento.
migrar
Planificar y ejecutar migración entre stacks tecnológicos o versiones mayores.
prd
Generar Product Requirement Document (PRD) completo desde múltiples fuentes — Figma, briefs, docs, research. Incluye análisis de riesgos, priorización RICE, user stories Gherkin y timeline. Usa cuando el usuario dice "PRD", "product requirements", "documento de producto", "requirements document", "generar PRD", "crear…
incorporar
Incorporar nuevo desarrollador al proyecto con contexto completo.
donde-estoy
Test rápido de 5 preguntas para verificar contexto.