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/fabriqaai/specs.md/agentgit clone --depth 1 https://github.com/fabriqaai/specs.mdWhat 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.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
agent 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
Agent Command
This file defines the agent command within the simple flow.
Command Definition
name: agent
description: Spec-driven development - create requirements, design, and tasks
Invocation
When this command is invoked, the agent should:
-
Load Context
- Read
.specsmd/simple/memory-bank.yaml - Read
.specsmd/simple/agents/agent.md - Scan
specs/for existing specs
- Read
-
Parse Arguments
$ARGUMENTScontains user input after command- Extract feature idea or spec name
- Determine intent (create, continue, update, execute)
-
Detect State
- If spec name provided, check for existing files
- Determine current phase based on file existence
-
Route to Skill
- NEW → requirements skill
- DESIGN_PENDING → design skill
- TASKS_PENDING → tasks skill
- COMPLETE → execute skill or offer updates
Usage Examples
/specsmd-agent Create a todo app with local storage
→ Creates new spec "todo-app", starts requirements phase
/specsmd-agent --spec="todo-app"
→ Continues existing spec at current phase
/specsmd-agent --spec="todo-app" --execute
→ Enter task execution mode for completed spec
/specsmd-agent
→ Lists existing specs or prompts for feature idea
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 · 61 lines · 0 tokens per session scan A 5395bc984491
agent is a command published in the GitHub repository fabriqaai/specs.md (205 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 314 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
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
constitution
Create or update the project constitution from interactive or provided principle inputs.
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
Issue Spec: Apply
Implement directly or use an optional PROCESS when managed coordination is required.
/spdd-story
Decompose high-level feature requirements into INVEST-compliant, business-focused stories with clear scope boundaries and testable acceptance criteria.
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.