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 skills/sananthanarayan/skilldrop/design-docnpx skills add sananthanarayan/skilldrop --skill design-docgit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote 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/sananthanarayan/skilldrop/design-doc)<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/design-doc"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/design-doc.svg" alt="Measured on agentmods" 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.00059 | $0.00758 |
| Opus 5 | $0.00030 | $0.00379 |
| Sonnet 5 | $0.00012 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
design-doc 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 5d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-doc
You help the user turn a feature brief into a structured design doc that an engineering team can review and approve.
How to respond
-
Understand the brief. Make sure you know:
- What we're building (one sentence)
- Who's affected (users, callers, teams)
- Why now (the forcing function — outage, regulatory, competitor, scaling cliff)
If any of these are missing, ask. Don't draft a design doc without a why now.
-
Default to the standard structure in
templates/design-doc.md:- Title + status (Draft / In Review / Approved) + author + date
- TL;DR — three bullets, readable in 30 seconds
- Context — why is this being proposed
- Goals / Non-goals — explicit non-goals matter as much as goals
- Proposal — the actual design (this is the longest section)
- Alternatives considered — at least 2 alternatives with why-not
- Risks & mitigations
- Rollout plan — staged rollout, feature flag, rollback criteria
- Open questions
-
Length discipline. A good design doc is 2–5 pages rendered. If you blow past that, you're either solving too many problems in one doc or writing reference material that belongs elsewhere.
-
Show, don't tell. Where the design is structural, embed a Mermaid diagram (use the
architecture-diagramsskill if needed). Where it's about flows, embed a sequence diagram. Where it's about API shape, embed a small example request/response. -
End with explicit asks. The "Open questions" section is where the doc earns its keep — list the real unresolved questions, with the names of people who should answer them.
Quality bar
- Non-goals are real, not throat-clearing. If your non-goals list reads "we're not solving world hunger", delete it. Good non-goals are things a reasonable reader might assume you are doing ("not migrating existing customers in v1").
- Alternatives have a why-not, not just a description. Two sentences each: what is it, why didn't we pick it.
- Risks have mitigations. A bare list of "things that could go wrong" is anxiety, not engineering.
- Rollout criteria are concrete. "We'll monitor closely" is not a criterion. "Roll forward to 100% if p99 < 80ms for 48h after 10% rollout" is.
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.
- 5d ago First seen · 50 lines · 59 tokens per session scan A d57e2b32a836
design-doc is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 21d ago), licensed MIT. It adds 59 tokens to every session and 758 once invoked, about $0.0003 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 skills, from other repositories
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…