status

status is a skill for Claude Code from drafthq/draft. It costs 22 tokens per session (1,563 once invoked), scanned A, original, MIT.

A progress report for Draft tracks and active tasks. A track is a planned stream of project work; the report shows its phases, completion percentages, blocked items, and related project files.

In plain words
What is it for?
Use it to check project progress, find blocked work, inspect active tracks, and identify tracks without matching records.
Why use it?
It prevents status updates from relying on guesses by requiring the project records to be read first. It also surfaces missing or unavailable status information.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the draft plugin — 33 skills shipped together

Good fit Use it to check project progress, find blocked work, inspect active tracks, and identify tracks without matching records.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drafthq/draft/status
Install

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.

Any agent
npx skills add drafthq/draft --skill status
Clone the repo
git clone --depth 1 https://github.com/drafthq/draft

Made for: Claude Code.

Or install draft, the plugin that ships this one along with the rest of its 33 skills.

Wrote 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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/skills/drafthq/draft/status/github.svg)](https://agentmods.dev/skills/drafthq/draft/status)
Your own site
<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.

agentmods 80×15 button for status

Your own site · 80×15
<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>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,563 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 0e63be0842f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/status/SKILL.md · 185 lines

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

  1. Read draft/tracks.md for track list
  2. For each active track, read:
    • draft/tracks/<id>/metadata.json for stats. If metadata.json is malformed or unreadable, display (metadata unavailable) for that track's statistics instead of failing.
    • draft/tracks/<id>/plan.md for task status
    • draft/tracks/<id>/architecture.md for module status (if exists)
    • metadata.json:scope_includes / scope_excludes for the track's scope footprint. Surface these in the status output so reviewers can spot overlap at a glance. Conflicts are detected by scripts/tools/check-scope-conflicts.sh (see core/shared/template-contract.md).
  3. Check for project-wide draft/.ai-context.md (or legacy draft/architecture.md) for module status
  4. Detect orphaned tracks:
    • Scan draft/tracks/ for all directories
    • For each directory, check if it has metadata.json
    • Cross-reference with draft/tracks.md entries
    • If directory has metadata.json but NOT in tracks.md → orphaned track
    • Collect list of orphaned track IDs for warning section

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

Read the full file on GitHub · 185 lines

Changes

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.

  1. 1mo ago First seen · 185 lines · 22 tokens per session scan A 0e63be0842f3

Subscribe to this mod's changes

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.