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 The-AI-Directory-Company/agents-and-skills --skill technical-spec-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/technical-spec-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/technical-spec-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/technical-spec-writing/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/the-ai-directory-company/agents-and-skills/technical-spec-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/technical-spec-writing.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.00038 | $0.01182 |
| Opus 5 | $0.00019 | $0.00591 |
| Sonnet 5 | $0.00008 | $0.00236 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
technical-spec-writing 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 9d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Spec Writing
Before you start
Gather the following from the user. If anything is missing, ask before writing:
- What are you building? — Feature name and one-sentence summary. Link to the PRD if one exists.
- Why now? — Business driver, user pain, or technical urgency behind this work.
- Scope — New feature, refactor, migration, or extension of an existing system?
- Constraints — Tech stack, timeline, team size, backward-compatibility requirements.
- Audience — Who reviews this spec? (e.g., engineering team, staff engineer, CTO, security)
If the user says "write a spec for X" with no context, push back: "What problem does this solve, and what does the system look like today?"
Technical spec template
Title
[Feature/Change Name] — Technical Specification
1. Problem Statement (3-5 sentences)
State the problem from the user's or system's perspective. Reference the PRD or incident that motivates the work. Describe the current state and why it is insufficient.
2. Context
Summarize relevant prior art: existing systems, past decisions, constraints inherited from other teams. A reviewer who has no background should understand the landscape after reading this section.
3. Proposed Solution
Describe the approach at a level of detail sufficient for another engineer to implement it. Include component interactions, sequence of operations, and key design decisions. Call out alternatives you considered and why you rejected them.
4. Data Model Changes
Document every schema change: new tables, columns, indexes, or type modifications. Use DDL or a clear table format. State whether changes are additive (safe to deploy independently) or breaking.
5. API Changes
For each new or modified endpoint: method, path, request/response shapes, error codes, and auth requirements. If no API changes, state "No API changes" explicitly so reviewers know it was considered.
6. Migration Plan
Step-by-step plan for moving from current state to target state. Include: ordering of deploys, data backfill strategy, estimated duration, and whether the migration requires downtime.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 101 lines · 38 tokens per session scan A f027689bd082
technical-spec-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,182 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-09-03.
Other skills, from other repositories
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
graphql-expert
GraphQL API design and implementation. Use when building GraphQL APIs, designing schemas, implementing resolvers, or optimizing GraphQL performance.
devex-sdk-design
Developer experience (DX) engineering, SDK design patterns, API ergonomics, CLI tooling design, documentation-driven development, and developer onboarding. Use when designing SDKs, improving API ergonomics, building developer tools, or creating developer documentation.
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
hunt-auth-bypass
Hunting skill for auth bypass vulnerabilities. Built from 4 public bug bounty reports. Use when hunting auth bypass on any target.