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/drafthq/draft/discovernpx skills add drafthq/draft --skill discovergit clone --depth 1 https://github.com/drafthq/draftWhat 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.00075 | $0.00780 |
| Opus 5 | $0.00037 | $0.00390 |
| Sonnet 5 | $0.00015 | $0.00156 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
discover 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover - Investigation & Quality Router
/draft:discover is the single front door for all investigation, auditing, pattern learning, and quality exploration activities.
When to Use
- Any debugging or root-cause work
- Code quality reviews (lightweight to exhaustive to architectural)
- Coverage analysis and test strategy design
- Discovering and codifying project conventions
- Project tours, impact analysis, or reviewer assistance
Routing Logic
Strong keyword and phrase matching with fallback to a menu when intent is broad or compound. Several quality commands auto-chain (e.g. review may call bughunt).
| User Intent Keywords | Dispatches To | Purpose |
|---|---|---|
| debug, investigate bug, reproduce, isolate, diagnose | /draft:debug |
Structured 4-phase debugging |
| hunt bugs, find bugs, exhaustive sweep, regression hunt | /draft:bughunt |
14-dimension bug hunt + regression tests |
| quick review, fast review, sanity check, lightweight review | /draft:quick-review |
4-dimension review (~2 min) |
| deep review, production audit, module audit, ACID compliance | /draft:deep-review |
Full module lifecycle + architecture audit |
| coverage, code coverage, test coverage report | /draft:coverage |
Coverage measurement and gap report |
| test strategy, testing plan, coverage targets, pyramid | /draft:testing-strategy |
Test approach design |
| learn patterns, discover conventions, update guardrails, anti-patterns | /draft:learn |
Pattern mining + guardrail evolution |
| tour, walkthrough, onboard me, getting started tour | /draft:tour |
Guided interactive project tour |
| blast radius, code impact, affected modules, downstream callers | /draft:review or scripts/tools/graph-impact.sh |
Graph-derived blast-radius before merge |
| impact, delivery telemetry, track analytics, CDD effectiveness | /draft:impact |
Project-wide track delivery telemetry |
| assist review, help reviewer, PR architectural audit | /draft:assist-review |
Risk audit to support human reviewers |
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 · 65 lines · 75 tokens per session scan A 36253449306b
discover is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 13d ago), licensed MIT. It adds 75 tokens to every session and 780 once invoked, about $0.0004 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-30.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.