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/eddiebelaval/squire/docsgit clone --depth 1 https://github.com/eddiebelaval/squireWhat 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.00426 |
| Opus 5 | $0.00000 | $0.00213 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
docs 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
/docs - Generate Documentation
You are creating plain-English documentation for a non-technical audience.
Documentation Types:
For Features
- What it does - One sentence
- Why it exists - User problem solved
- How to use it - Step by step
- What to expect - Normal behavior
- Edge cases - What if scenarios
For Components
- Purpose - What is it for?
- Where it's used - Which pages/features?
- Key behaviors - What does it do?
- Props/Options - What can be configured?
- Visual examples - Screenshots if applicable
For APIs/Endpoints
- What it does - Purpose
- When to use - Use cases
- Input - What it needs
- Output - What it returns
- Example - Real-world usage
Style Guidelines:
Do:
- ✅ Use simple, conversational language
- ✅ Explain WHY, not just WHAT
- ✅ Include examples
- ✅ Use analogies
- ✅ Add emojis for visual breaks
- ✅ Focus on user value
Don't:
- ❌ Use technical jargon
- ❌ Show code unless essential
- ❌ Assume technical knowledge
- ❌ Write for developers
- ❌ Skip the "why"
Output Format:
# [Feature Name]
## 🎯 What It Does
[One clear sentence]
## 💡 Why It Exists
[The problem it solves]
## 🚀 How to Use It
1. [Step one]
2. [Step two]
3. [Step three]
## ✨ What to Expect
[Normal behavior description]
## 🤔 Edge Cases
- **Scenario**: What happens
- **Scenario**: What happens
## 📸 Visual Guide
[Screenshots if applicable]
Remember: Write as if explaining to a smart friend who isn't technical.
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 · 73 lines · 0 tokens per session scan A dc7552515709
docs is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 426 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-30.
Other commands, from other repositories
deck
Turn a markdown planning doc into a spec-grade 기획서 HTML — a buildless, self-contained document by default, or an on-screen slide presentation when you ask for one. Deterministic md→deck transform + a quality/gap lint; the raw markdown travels with it. Use whenever the user wants a planning document turned into…
regression
Run accumulated regression across scv/archive//TESTS.md (and optionally promote/) with supersede/obsolete skip graph. On failure, triage each slug via AskUserQuestion (regression / obsolete / flaky). Use whenever the user asks whether past features still pass, or before archiving anything — 'run the tests', 'is…
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
handoff
Declare that another repo needs corresponding development: write a handoff (+ decision + conversation) into the workspace root scv repo. Multi-repo (nested) only. Use whenever work in this repo implies a change another repo must make — not only when they type /scv:handoff. Never leave that dependency in prose; this…
status
Show raw changes since last index + list of active promote plans. Use whenever the user asks what is in flight, what changed, or where things stand — not only when they type /scv:status. Never summarize project state from memory; this command reads it.
update
Check installed SCV plugin version vs latest release, and guide the user through /plugin marketplace update + /reload-plugins. Read-only — does not modify project files. (v0.11.2+) Use whenever the user asks whether SCV is current or how to update it — not only when they type /scv:update.