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 skills add drafthq/draft --skill statusgit clone --depth 1 https://github.com/drafthq/draftWrote 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/drafthq/draft/status)<a href="https://agentmods.dev/skills/drafthq/draft/status"><img src="https://agentmods.dev/badge/skills/drafthq/draft/status/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/drafthq/draft/status"><img src="https://agentmods.dev/badge/skills/drafthq/draft/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01563 |
| Opus 5.5 | $0.00009 | $0.00625 |
| Sonnet 5.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 1mo 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.
- 1mo 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 10d ago), licensed MIT. It adds 22 tokens to every session and 1,563 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-08-30.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
skill-creator
Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.