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/statusnpx skills add drafthq/draft --skill statusgit 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.00022 | $0.01563 |
| Opus 5 | $0.00011 | $0.00781 |
| Sonnet 5 | $0.00004 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
status 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Status
Display a comprehensive overview of project progress.
Red Flags - STOP if you're
- Reporting status without actually reading the files
- Making up progress percentages
- Skipping blocked items in the report
- Not checking each active track's actual state
- Summarizing without evidence from the files
Always read before reporting.
Gather Data
- Read
draft/tracks.mdfor track list - For each active track, read:
draft/tracks/<id>/metadata.jsonfor stats. Ifmetadata.jsonis malformed or unreadable, display(metadata unavailable)for that track's statistics instead of failing.draft/tracks/<id>/plan.mdfor task statusdraft/tracks/<id>/architecture.mdfor module status (if exists)metadata.json:scope_includes/scope_excludesfor the track's scope footprint. Surface these in the status output so reviewers can spot overlap at a glance. Conflicts are detected byscripts/tools/check-scope-conflicts.sh(see core/shared/template-contract.md).
- Check for project-wide
draft/.ai-context.md(or legacydraft/architecture.md) for module status - Detect orphaned tracks:
- Scan
draft/tracks/for all directories - For each directory, check if it has
metadata.json - Cross-reference with
draft/tracks.mdentries - If directory has metadata.json but NOT in tracks.md → orphaned track
- Collect list of orphaned track IDs for warning section
- Scan
Optional: report rollup & freshness signals
If parse-reports.sh and freshness-check.sh are available, gather structured signals to enrich the status output (severity counts per track, stale draft/ docs). Resolve via the canonical tool resolver (see core/shared/tool-resolver.md):
DRAFT_TOOLS="${DRAFT_PLUGIN_ROOT:-$(cat ~/.cache/draft/plugin-root 2>/dev/null)}/scripts/tools"
[ -d "$DRAFT_TOOLS" ] || DRAFT_TOOLS="$(ls -d ~/.claude/plugins/cache/*/draft/*/scripts/tools 2>/dev/null | sort -V | tail -1)"
[ -d "$DRAFT_TOOLS" ] || DRAFT_TOOLS="$(ls -d ~/.claude/plugins/marketplaces/*draft*/scripts/tools 2>/dev/null | tail -1)"
[ -d "$DRAFT_TOOLS" ] || DRAFT_TOOLS="$PWD/scripts/tools"
# Per-track report severity rollup (bughunt, review, tech-debt, etc.):
[ -x "$DRAFT_TOOLS/parse-reports.sh" ] && \
bash "$DRAFT_TOOLS/parse-reports.sh" --root draft/
# Stale draft/ docs (sha256 drift since last index):
[ -x "$DRAFT_TOOLS/freshness-check.sh" ] && [ -f draft/.state/freshness.json ] && \
bash "$DRAFT_TOOLS/freshness-check.sh" --state draft/.state/freshness.json
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 · 185 lines · 22 tokens per session scan A 0e63be0842f3
status is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 1,563 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-30.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
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.