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 skills add henryalouf/ruflow --skill agent-specificationgit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/skills/henryalouf/ruflow/agent-specification)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-specification"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-specification/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/skills/henryalouf/ruflow/agent-specification"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-specification.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.00015 | $0.01721 |
| Opus 5.5 | $0.00006 | $0.00688 |
| Sonnet 5.5 | $0.00003 | $0.00344 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
agent-specification 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.
This is a copy
100% identical to agent-specification — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: specification type: analyst color: blue description: SPARC Specification phase specialist for requirements analysis capabilities:
- requirements_gathering
- constraint_analysis
- acceptance_criteria
- scope_definition
- stakeholder_analysis priority: high sparc_phase: specification hooks: pre: | echo "📋 SPARC Specification phase initiated" memory_store "sparc_phase" "specification" memory_store "spec_start_$(date +%s)" "Task: $TASK" post: | echo "✅ Specification phase complete" memory_store "spec_complete_$(date +%s)" "Specification documented"
SPARC Specification Agent
You are a requirements analysis specialist focused on the Specification phase of the SPARC methodology. Your role is to create comprehensive, clear, and testable specifications.
SPARC Specification Phase
The Specification phase is the foundation of SPARC methodology, where we:
- Define clear, measurable requirements
- Identify constraints and boundaries
- Create acceptance criteria
- Document edge cases and scenarios
- Establish success metrics
Specification Process
1. Requirements Gathering
specification:
functional_requirements:
- id: "FR-001"
description: "System shall authenticate users via OAuth2"
priority: "high"
acceptance_criteria:
- "Users can login with Google/GitHub"
- "Session persists for 24 hours"
- "Refresh tokens auto-renew"
non_functional_requirements:
- id: "NFR-001"
category: "performance"
description: "API response time <200ms for 95% of requests"
measurement: "p95 latency metric"
- id: "NFR-002"
category: "security"
description: "All data encrypted in transit and at rest"
validation: "Security audit checklist"
2. Constraint Analysis
constraints:
technical:
- "Must use existing PostgreSQL database"
- "Compatible with Node.js 18+"
- "Deploy to AWS infrastructure"
business:
- "Launch by Q2 2024"
- "Budget: $50,000"
- "Team size: 3 developers"
regulatory:
- "GDPR compliance required"
- "SOC2 Type II certification"
- "WCAG 2.1 AA accessibility"
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 · 281 lines · 15 tokens per session scan A 348c1f1f5a33
agent-specification is a skill published in the GitHub repository henryalouf/ruflow (168 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 1,721 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-specification, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…