agent-specification

agent-specification is a skill for Claude Code from Soulcynics404/AgentForge. It costs 15 tokens per session (1,721 once invoked), scanned A, a copy of agent-specification, MIT.

A requirements-analysis skill for the Specification phase of the SPARC development method. It turns a software idea into defined requirements, constraints, acceptance checks, and edge cases.

In plain words
What is it for?
Use it to gather requirements, define scope, document user stories and edge cases, and write testable acceptance criteria.
Why use it?
It helps replace vague requests with a clear description of what must be built and how to decide whether it is correct.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the claude-flow plugin — 134 skills, 52 commands, 11 agents, 4 hooks, 1 MCP server shipped together

Good fit Use it to gather requirements, define scope, document user stories and edge cases, and write testable acceptance criteria.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/soulcynics404/agentforge/agent-specification
Install

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.

Any agent
npx skills add Soulcynics404/AgentForge --skill agent-specification
Clone the repo
git clone --depth 1 https://github.com/Soulcynics404/AgentForge

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 134 skills, 52 commands, 11 agents, 4 hooks, 1 MCP server.

Wrote 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.

agentmods badge for agent-specification

README.md
[![agentmods](https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-specification/github.svg)](https://agentmods.dev/skills/soulcynics404/agentforge/agent-specification)
Your own site
<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-specification"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/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.

agentmods 80×15 button for agent-specification

Your own site · 80×15
<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-specification"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-specification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,721 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 348c1f1f5a33, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

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.

.agents/skills/agent-specification/SKILL.md · 281 lines

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:

  1. Define clear, measurable requirements
  2. Identify constraints and boundaries
  3. Create acceptance criteria
  4. Document edge cases and scenarios
  5. 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"

Read the full file on GitHub · 281 lines

Changes

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.

  1. 1mo ago First seen · 281 lines · 15 tokens per session scan A 348c1f1f5a33

Subscribe to this mod's changes

agent-specification is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 1mo 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.

Related

Other skills, from other repositories

migrating-vercel-ai-sdk-and-eve-to-pydantic-ai

Migrate TypeScript Vercel AI SDK or Eve applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports ai, @ai-sdk/, or eve, or relies on generateText, streamText, ToolLoopAgent, useChat, Eve agents, tools, skills, subagents, approvals, sessions, channels, schedules…

pydantic/pydantic-ai · 107 tokens

migrating-mastra-to-pydantic-ai

Migrate TypeScript Mastra applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports @mastra/ or relies on Mastra agents, tools, workflows, memory, processors, streaming, approvals, skills, or subagents.

pydantic/pydantic-ai · 73 tokens

migrating-openai-agents-sdk-to-pydantic-ai

Migrate Python OpenAI Agents SDK applications to Pydantic AI and, when warranted, Pydantic AI Harness. Use for agents.Agent, Runner, function tools, handoffs, guardrails, sessions, human approval, streaming, or SandboxAgent. Do not use for applications built directly on the OpenAI Responses API without the Agents SDK…

pydantic/pydantic-ai · 87 tokens

hephaestus-network

Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.

agentlas-ai/Agentlas-OS · 75 tokens

hep-upload

Publish an Agentlas package to Agent Cloud or the public Hub.

agentlas-ai/Agentlas-OS · 16 tokens

research-report

Research report on companies, competitors, markets or products: research a company, compare competitors, market landscape, funding, pricing, launches. Also to save a brief, summary or snapshot built from search results.

ShenSeanChen/waku-agent · 0 tokens