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/documentnpx skills add Maximumsoft-Co-LTD/claude-flightdeck --skill documentgit clone --depth 1 https://github.com/Maximumsoft-Co-LTD/claude-flightdeckWhat 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.00076 | $0.01630 |
| Opus 5 | $0.00038 | $0.00815 |
| Sonnet 5 | $0.00015 | $0.00326 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
document scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
trust a curl response for SPA pages. How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/document — Generate / Sync Project Documentation
Generate user-facing or contract-facing documentation from the source of truth (live system, OpenAPI / proto / GraphQL schema, in-repo design docs, or screenshots from a real browser). The skill picks the right source for the request and loads the matching variant reference.
Token budget (MANDATORY)
- Use Grep to discover existing docs before regenerating — don't rewrite what's already there.
- Read the live spec / contract / schema as the canonical source.
- For UI screenshots, drive a real browser (Playwright MCP) — never trust a curl response for SPA pages.
Usage
/document— full sync (regenerates everything in scope)/document <module>— sync one module / endpoint group / feature/document status— show coverage (documented vs existing)/document refresh— re-capture + update existing pages/document export— emit deployable artifact (SQL seed / static site / SDK package)
Prerequisites check
Before any generation step, verify:
- The source-of-truth is reachable (live service / spec file / repo).
- If screenshots are part of the output: the frontend + backend are running, and Playwright MCP is available.
- Output directory exists and is writable.
If any prerequisite fails → tell the user what's missing and stop.
Steps
1. Discover scope
Glob existing docs; Grep the source of truth; compute the diff
(what's documented vs what exists). Read docs/.manifest.json (or the
per-scope manifest) to know what was generated by which tool.
2. Pick the right variant — load the matching reference
| If the source is... | Load before generating |
|---|---|
contracts/openapi/*.yaml or *.json |
references/api-openapi.md |
contracts/proto/**/*.proto (or proto/**) |
references/api-proto.md |
| The live UI (screenshots / walkthrough) | references/user-guide-playwright.md |
| The contract → SDK code (any language) | references/sdk-codegen.md |
| Always (for the manifest schema + refresh logic) | references/manifest-format.md |
What ships with it
5 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.
- 3d ago First seen · 189 lines · 76 tokens per session scan A 0d638a3e38f1
document is a skill published in the GitHub repository Maximumsoft-Co-LTD/claude-flightdeck (2 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 1,630 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-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-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-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.