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 commands/markdavidgan/apple-dev-skills/write-specgit clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsWhat 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 | $0.00020 | $0.00112 |
| Opus 5 | $0.00010 | $0.00056 |
| Sonnet 5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
write-spec 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 2d 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.
What it actually says
Run the product-spec skill on $ARGUMENTS.
Turns an idea into a buildable, verifiable spec: problem statement, goals and non-goals, user stories, testable Given/When/Then acceptance criteria, success metrics with targets and windows, scope/phases, and open questions. Produces a document that feeds verify-against-spec and complete-feature.
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.
- 2d ago First seen · 9 lines · 20 tokens per session scan A 5655a0910145
write-spec is a command published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 112 once invoked, about $0.0001 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 commands, from other repositories
agent-build-feature
A strict brief that makes a coding agent implement a feature end to end, matching the codebase and verifying it works.
agent-fix-bug
A strict brief that makes a coding agent find the root cause of a bug, fix it minimally, and prove it is fixed.
agent-system-prompt
Write a system prompt for an AI agent that defines its role, tools, boundaries, and output clearly enough to act reliably.
agent-task-breakdown
Decompose a complex task into clear subtasks an AI agent (or agents) can execute and verify step by step.
api-docs-from-code
Generate accurate reference documentation for an API from its code, marking every inference.
bug-report-triage
Turn a vague bug report into a structured, actionable ticket with severity and next steps.