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 tomzx/agents --skill create-specificationsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/create-specifications)<a href="https://agentmods.dev/skills/tomzx/agents/create-specifications"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-specifications/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/tomzx/agents/create-specifications"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-specifications.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 29 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 97 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 29 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 98 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00025 | $0.01461 |
| Opus 5.5 | $0.00010 | $0.00584 |
| Sonnet 5.5 | $0.00005 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
create-specifications 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 22d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Specifications
Produces a detailed technical specification from a requirements document, covering architecture, data models, API contracts, component design, and key sequences.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. .sdlc/features/N-<slug>/requirements.md(must have passed review with findings verdictapproved), or a requirements document provided in context or as a file path ($1).sdlc/features/N-<slug>/existing-solutions.md(optional, if a prior-art survey was produced): adopt its recommendation and reuse the patterns it captured.sdlc/features/N-<slug>/codebase-analysis.md(optional, if existing code was analyzed): follow each component's change disposition and its "must not change" constraints, and follow the migration path for any refactor or replace
Steps
- Read and understand the requirements document, the existing solutions survey if present, and the codebase analysis if present.
- Identify the major components and their responsibilities.
- Define data models: entities, attributes, and relationships.
- Specify API contracts: endpoints, request/response schemas, and error codes.
When the feature defines an API surface, write the normative contract to
.sdlc/features/N-<slug>/api.yaml(OpenAPI 3, template atskills/sdlc/templates/features/api.yaml) and keep only a summary table inspecification.md, so the contract is lintable and diffable instead of prose. - Describe key sequences as Mermaid
sequenceDiagramblocks (one per flow): user flows, system interactions, and async processes. A message with no receiver makes a missing step obvious before code exists. - Document technical decisions and their rationale.
- Identify risks, unknowns, and deferred decisions.
- Design data models, API contracts, and persisted state for evolution so future versions stay forward compatible (see Forward Compatibility below).
- Validate best-effort: lint
api.yamlwithnpx -y @stoplight/spectral-cli lint api.yamland render eachmermaidblock withmmdc(ornpx -y @mermaid-js/mermaid-cli) when available. A missing tool is not a failure; skip and note it. A validation failure is a defect to fix before handoff. - Write the output to
.sdlc/features/N-<slug>/specification.md(plusapi.yamlwhen the feature has an API surface).
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.
- 22d ago Changed · +8 lines 479c550081bf
- 24d ago Changed c4549fbf7e6c
- 2mo ago First seen · 99 lines · 25 tokens per session scan A 5e44cc886e35
create-specifications is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,461 once invoked, about $0.0001 per session on Opus 5.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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…