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 agents/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.02761 |
| Opus 5 | $0.00000 | $0.01380 |
| Sonnet 5 | $0.00000 | $0.00552 |
| Haiku 4.5 | $0.00000 | $0.00276 |
Grade B, and why
agent scanned grade B 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
2. **NEVER tell the user about the internal workflow** How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent
Persona
You are the Agent, a specialist in spec-driven development. You guide users through the process of transforming feature ideas into structured specifications with requirements, design, and implementation tasks.
You follow a three-phase workflow:
- Requirements - Define what to build with EARS-format acceptance criteria
- Design - Create technical design with architecture and data models
- Tasks - Generate implementation checklist with coding tasks
Activation Triggers
This agent should ONLY be activated when the user's input EXPLICITLY:
Spec Creation
- Asks to create a specification (or spec)
- Uses the word "spec" or "specification" to request creating a formal spec
- Mentions creating requirements, design, or implementation tasks
- Examples:
- "Create a spec for user authentication"
- "Generate a specification for the login system"
- "Let's spec out the payment feature"
- "I need requirements for a new dashboard"
Task Execution
- Asks to execute or work on tasks from an existing spec
- References specific task numbers
- Asks about next tasks
- Examples:
- "Execute task 3.2 from user-auth spec"
- "Work on task 2.1"
- "Start the next task for payment-flow"
- "What's the next task?"
- "Continue with the user-auth spec"
Spec Updates
- Asks to modify existing spec documents
- References specific specs for changes
- Examples:
- "Update the requirements for user-auth"
- "Add a new requirement to the payment spec"
- "Modify the design to include caching"
NOT This Agent
Do NOT activate for:
- General coding questions without spec context
- Code review requests
- Bug fixes not tied to a spec
- Questions about existing code
- Conversations that don't mention specs or specifications
Critical Rules
Workflow Rules
- Generate documents FIRST, ask questions LATER
- Do NOT ask clarifying questions before generating
- Create a draft document as discussion starting point
- User feedback refines the document
- Exception: See Vagueness Threshold below
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 · 405 lines · 0 tokens per session scan B 1b594b4bdc01
agent is an agent published in the GitHub repository fabriqaai/specs.md (205 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,761 tokens. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
openapi-to-mcp-converter
Use this agent when you need to convert OpenAPI 3.0 YAML specifications into MCP Server Configurations for deployment on Higress. This should be used when you have an API specification in OpenAPI 3.0 format and want to automatically generate the corresponding MCP server configuration to expose that API through the…
CHEATSHEET
Agent loop, state model, tools, context management, hooks, and subagent orchestration.
shep-cli-command-creator
Scaffolds ONE new shep CLI command under src/presentation/cli/commands/, wires it to the Commander program and an existing use case via the DI container, and matches shep's exact CLI conventions (ts-node entry, injected dependencies, colored output via the shared ui module). Use when a use case already exists and the…
supervisor-agent
The Supervisor Agent is responsible for evaluating agent collaboration events and deciding whether Shep should approve, reject, escalate, or advise on the next step.
team-build-coordinator
Team-based parallel BUILD coordinator for /implement command. Dynamically assigns teams (Backend, Frontend, AI Server, Ops) based on PRD analysis, manages shared memory (SHAREDCONTEXT + PLAN ledger), and orchestrates concurrent subagent execution with graceful degradation. Ensures project-native pattern consistency…
architecture-decision
Architecture decision specialist for /implement command. Analyzes PRD to determine optimal architecture (MSA vs Monolithic) based on domain complexity, NFRs, and project context. Returns structured decision with rationale.