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 mickpletcher/AI-Skills --skill spec-writergit clone --depth 1 https://github.com/mickpletcher/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/mickpletcher/ai-skills/spec-writer)<a href="https://agentmods.dev/skills/mickpletcher/ai-skills/spec-writer"><img src="https://agentmods.dev/badge/skills/mickpletcher/ai-skills/spec-writer/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/mickpletcher/ai-skills/spec-writer"><img src="https://agentmods.dev/badge/skills/mickpletcher/ai-skills/spec-writer.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.00026 | $0.01218 |
| Opus 5.5 | $0.00010 | $0.00487 |
| Sonnet 5.5 | $0.00005 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
spec-writer 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Writer Skill
Intent
Use this skill to turn a rough repo change, feature idea, cleanup effort, or migration into a numbered spec folder with practical planning documents. The goal is to create a working spec package that another engineer can pick up and execute without guessing what the work means.
Use When
- The user wants a new spec for a repo change, feature, refactor, migration, or workflow
- A project needs structured
requirements.md,plan.md, andtasks.mddocuments - The repo already uses numbered spec folders and new work should follow that pattern
- The request is large enough that ad hoc notes would be too loose
Do Not Use When
- The change is tiny and does not need formal planning
- The repo has no spec workflow and the user only wants direct implementation
- The user wants a README, assessment, or changelog instead of an execution spec
- The available context is too thin to produce honest requirements and next steps
Workflow
- Read the repo context first.
- Confirm where specs live and how numbering works.
- Pick the next available spec number unless the user provided one.
- Create a short kebab case spec folder name tied to the actual work.
- Write the core documents:
requirements.mdplan.mdtasks.md
- Keep each file practical:
- requirements explain the problem, scope, constraints, and success criteria
- plan explains the implementation approach, touched areas, risks, and validation path
- tasks break the work into ordered, checkable execution steps
- Make assumptions explicit. Do not pretend unknown details are settled facts.
- Recheck that the spec matches the live repo, existing conventions, and the user's real goal.
Spec Status
Give every spec a visible state so a folder listing tells the truth about the work. Put a status line at the top of requirements.md:
Status: draft | in progress | done | abandoned
Last updated: YYYY-MM-DD
When asked to update or review specs, update the status line as part of the change. When creating a new spec, check whether an existing spec already covers the work and is merely stale; updating its status beats creating a duplicate.
What ships with it
4 files 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.
- 1mo ago First seen · 134 lines · 26 tokens per session scan A 3b8728f16a9d
spec-writer is a skill published in the GitHub repository mickpletcher/AI-Skills (20 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,218 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-30.
Other skills, from other repositories
multai
Intelligent Multi-AI Router & Orchestrator. Submits prompts to 7 AI platforms simultaneously (or sequentially in Cowork) and synthesizes results. Supports two runtimes automatically detected at startup: • Code tab (Mac): Playwright/Browser-Use engine — parallel, full-featured • Cowork tab (Linux sandbox)…
comparator
Generic Comparison Matrix Builder: creates, populates, and maintains weighted XLSX comparison matrices for ANY domain and ANY pair (or set) of solutions. Evidence comes from whatever is available — CIRs produced by MultAI's solution-researcher, documents in the working folder, LLM knowledge, or user description. A CIR…
consolidator
Generic Multi-Source Consolidator: synthesizes content from any set of input sources — documents, research notes, interview transcripts, meeting summaries, AI platform responses, or any mix — into a unified, well-structured report. When invoked with a raw AI responses archive (produced by the orchestrator or a…
landscape-researcher
Market Landscape Researcher: orchestrates a full end-to-end landscape research workflow for any software solution category. Builds a research prompt from a proven template, runs it across 7 AI platforms in parallel (via the orchestrator skill), synthesises the responses into a structured 9-section Market Landscape…
solution-researcher
Orchestrates a simultaneous 7-AI competitive intelligence research round on any software product. Builds a capability-analysis prompt from a template, invokes the orchestrator engine, then invokes the consolidator skill to produce a Consolidated Intelligence Report (CIR). USE THIS SKILL whenever the user asks to…
multai:update
Check for MultAI updates, show changelog, and install if available.