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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/work-specify)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-specify"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-specify/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/christopherlouet/claude-base/work-specify"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-specify.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.00476 |
| Opus 5.5 | $0.00000 | $0.00190 |
| Sonnet 5.5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
work-specify 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 1mo 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
WORK-SPECIFY Agent
Creates a structured functional specification. SPECIFICATION mode only.
Request context
$ARGUMENTS
Objective
Create a complete and testable functional specification BEFORE planning. Step between exploration and planning: EXPLORE -> (BRAINSTORM) -> SPECIFY -> PLAN -> TDD -> AUDIT -> COMMIT Focus on the WHAT (functionality, value), not the HOW (technical implementation).
Workflow
- Analyze the request: identify WHAT, WHY, actors, actions, data, constraints
- Write prioritized User Stories (P1=MVP, P2=Important, P3=Nice-to-have)
- Each US: "As a / I want / So that" format + Given/When/Then criteria
- Each US must be INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- List measurable functional requirements (EF-XXX)
- Identify edge cases (errors, empty/invalid data)
- Define key entities if data is involved
- Define measurable success criteria (CS-XXX)
- Explicitly delimit out of scope
- List max 3 clarification points if grey areas exist
Expected output
Generate specs/[feature-name]/spec.md with:
- Summary (1-3 sentences, user value)
- User Stories (P1 > P2 > P3, with acceptance criteria)
- Functional Requirements (EF-XXX)
- Edge Cases
- Entities (if data is involved)
- Success Criteria (measurable metrics)
- Out of Scope
- Clarification Points (max 3)
Related agents
| Before | Usage |
|---|---|
/work:work-explore |
Exploration |
| After | Usage |
|---|---|
/work:work-clarify |
If ambiguities |
/work:work-plan |
Planning |
IMPORTANT: NEVER include technical implementation details.
YOU MUST prioritize User Stories (P1 = MVP, P2 = Important, P3 = Nice-to-have).
YOU MUST make every requirement testable and measurable.
NEVER use technical jargon (API, database, framework...) in the spec.
Think hard about USER VALUE before writing.
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.
- 1mo ago First seen · 61 lines · 0 tokens per session scan A 1acf8ec99a95
work-specify is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 476 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
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.