Borrowing it
Nothing to install: this file belongs to sethdford/shipwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sethdford/shipwright/main/.claude/skills/write-adr/SKILL.mdgit clone --depth 1 https://github.com/sethdford/shipwrightWrote 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/sethdford/shipwright/write-adr)<a href="https://agentmods.dev/skills/sethdford/shipwright/write-adr"><img src="https://agentmods.dev/badge/skills/sethdford/shipwright/write-adr/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/sethdford/shipwright/write-adr"><img src="https://agentmods.dev/badge/skills/sethdford/shipwright/write-adr.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.00027 | $0.00132 |
| Opus 5.5 | $0.00011 | $0.00053 |
| Sonnet 5.5 | $0.00005 | $0.00026 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
write-adr 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 14d 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
Create docs/adr/NNNN-kebab-title.md with the next number and these sections:
# NNNN. Title, Status: accepted|superseded by NNNN, Date, ## Context (forces and
constraints), ## Decision (one paragraph), ## Consequences (what gets easier, what gets harder).
Keep it under 60 lines. Link it from docs/architecture.md if it changes the structure.
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.
- 14d ago First seen · 9 lines · 27 tokens per session scan A 9aac36ba4d3d
write-adr is a skill published in the GitHub repository sethdford/shipwright (21 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 132 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-10-15.
Other skills, from other repositories
code-review
Perform comprehensive code reviews covering bugs, style, performance, security, and best practices. Use this skill when the user mentions: review my code, check this code, code review, find bugs, improve code, refactor suggestions, security audit, performance optimization, code quality, static analysis.
team-coordination
Coordinate software development work by analyzing requirements, delegating tasks to specialized sub-agents (developer, code-reviewer, tester), and synthesizing their work into cohesive deliverables. Use this for complex projects that require multiple specialized perspectives.
test-writing
Write comprehensive tests for code including unit tests, integration tests, and end-to-end tests. Use this to ensure code quality, catch bugs, and validate functionality.
feature-implementation
Implement software features, fix bugs, and write production-quality code. Use this for hands-on development work including writing new code, modifying existing code, and debugging issues.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.