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/maximumsoft-co-ltd/claude-flightdeck/statusnpx skills add Maximumsoft-Co-LTD/claude-flightdeck --skill statusgit clone --depth 1 https://github.com/Maximumsoft-Co-LTD/claude-flightdeckWrote 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/maximumsoft-co-ltd/claude-flightdeck/status)<a href="https://agentmods.dev/skills/maximumsoft-co-ltd/claude-flightdeck/status"><img src="https://agentmods.dev/badge/skills/maximumsoft-co-ltd/claude-flightdeck/status.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 | $0.00130 | $0.01258 |
| Opus 5 | $0.00065 | $0.00629 |
| Sonnet 5 | $0.00026 | $0.00252 |
| Haiku 4.5 | $0.00013 | $0.00126 |
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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/status — Sprint Dashboard + Audit Digest
Read-only. Never writes, never edits any file.
Announce: Using /status — [sprint dashboard / audit digest].
Token budget
Dashboard (/status):
- One
Readof the active board (limit: 200) — header + task table. - All other queries via
Grep(status counts, blockers, per-component rollup). - Scope any
git logto the sprint window only (stale-task detection).
Audit (/status audit):
- Delegate to
scripts/query.sh— all JSONL aggregation happens injq+ bash. - Do NOT
Readaudit JSONL into model context (can be megabytes/month); always pipe through the script, which emits markdown to stdout — surface it verbatim.
Mode 1 — /status (sprint progress dashboard)
Reads docs/project/sprints/S<N>/tasks.md + docs/project/backlog.md.
- Find the active board —
Glob docs/project/sprints/*/tasks.md, pick the one whose Glance header marks it active. - Read the task table (
limit: 200). - Compute metrics — Total / Done
[x]/ In-progress[~]/ Not-started[ ]/ Blocked[B]/ completion %. - Print the dashboard:
## Sprint S<N>: <theme> Progress: [======> ] X/Y (Z%) | Task ID | Component | State | Owner | Blocker | |---|---|---|---|---| - Per-component / per-repo rollup:
| Component | Done | In progress | Remaining |. - Flag stale tasks —
[~]for >2 days (boardLast updateorgit log -1on the task's design doc). - Scan
docs/project/backlog.md## Follow-upsfor open items relevant to the sprint and list them.
Rules: read-only — never mutate. No active board → suggest /work to start
one or /recover if state is unclear.
Mode 2 — /status audit [week|sprint] (audit digest)
Aggregates docs/project/audit/*.jsonl (written by .claude/hooks/audit.sh)
into a digest: dispatches per agent with p50/p95 latency, slowest dispatches,
file-touch hotspots, task-ID retry counts, gate-failure indicators. Raw jq
recipes for ad-hoc work: references/jq-recipes.md.
What ships with it
2 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.
- 4d ago First seen · 100 lines · 130 tokens per session scan A 52af0393fae5
status is a skill published in the GitHub repository Maximumsoft-Co-LTD/claude-flightdeck (2 stars, last pushed 2mo ago), licensed MIT. It adds 130 tokens to every session and 1,258 once invoked, about $0.0006 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
vc-agent-strategy-compare
Evaluate 4 execution strategies (sequential, parallel-subagents, workflow, agent-team) for a phase or fan-out task. Outputs 7-signal score table, agent count math, cost guards, and strategy recommendation.
vc-generate-phase-program
Generate kickoff artifacts for a multi-phase program: umbrella plan, Program Goal Charter, session-goal block, per-phase plan stubs, and the 7-step per-phase inner loop reference.
vc-intent-clarify
Clarify intent before RIPER-5 phase delegation. Scores ambiguity (4 signals); generates structured multi-choice questions for Tier 2. Two-mode: SIMPLE and DEEP.
vc-autoresearch
Loop: find gaps → fix → repeat until agents find no gaps or a metric goal is hit. Shared loop primitive for PVL, EVL, and standalone quality runs.
vc-generate-closeout
Generate the post-EXECUTE closeout packet for a plan or phase. Includes archive-readiness classification, drift signal scoring, commit checkpoint recommendation, and move-on next-state recommendation.
vc-validate-findings
Use when running VALIDATE V2-V3 fan-out. Two-layer investigation (4 dimension agents + per-section feasibility agents) synthesized into PASS/CONDITIONAL/BLOCKED net gate. Strategy-agnostic.