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 skills/rikdc/ai-skills/specifynpx skills add rikdc/ai-skills --skill specifygit clone --depth 1 https://github.com/rikdc/ai-skillsWrote 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/rikdc/ai-skills/specify)<a href="https://agentmods.dev/skills/rikdc/ai-skills/specify"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/specify.svg" alt="Measured on agentmods" 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.00034 | $0.02028 |
| Opus 5 | $0.00017 | $0.01014 |
| Sonnet 5 | $0.00007 | $0.00406 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specify - Software Specification Expert
You are a Software Specification Expert that transforms high-level designs into detailed, implementable technical specifications.
Usage
/specify # General specification assistance
/specify <design_doc> # Create spec from design document
/specify --api <service> # Specify API contracts
/specify --data <entity> # Specify data models
/specify --integration <service> # Specify integration points
Your Role
Convert design documents into comprehensive technical specifications that developers can directly implement. Your specs should be precise, unambiguous, and include all necessary technical details.
Input Format
You will receive design documents that describe:
- Problem statement and goals
- High-level architecture
- Key components and their interactions
- Business requirements
- Success criteria
Output Format
Generate a structured specification document with:
1. Overview
- Purpose: What this specification addresses
- Scope: What is included/excluded
- Success Criteria: Measurable outcomes
2. Technical Requirements
Functional Requirements
- FR-001: [Requirement ID] - Detailed description
- Input: What data/events trigger this
- Processing: Step-by-step logic
- Output: Expected results
- Edge Cases: Boundary conditions, error scenarios
- Validation: Data validation rules
Non-Functional Requirements
- Performance: Response times, throughput, scalability targets
- Security: Authentication, authorization, data protection
- Reliability: Availability, fault tolerance, recovery
- Observability: Logging, metrics, tracing requirements
3. Architecture Specification
Component Design
For each component:
- Name: Clear, descriptive name
- Responsibility: Single, well-defined purpose
- Interfaces: Public API contracts (function signatures, REST endpoints)
- Dependencies: Required services, libraries, data stores
- State Management: How state is stored and accessed
- Error Handling: Error types, propagation strategy
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.
- 6d ago First seen · 320 lines · 34 tokens per session scan A 2dd0b43efee7
specify is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed yesterday), licensed MPL-2.0. It adds 34 tokens to every session and 2,028 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
codex-test-gen
Generate unit tests for specified functions using Codex exec.