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 Guohao1020/docs-cockpit --skill use-docs-cockpitgit clone --depth 1 https://github.com/Guohao1020/docs-cockpitWrote 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/guohao1020/docs-cockpit/use-docs-cockpit)<a href="https://agentmods.dev/skills/guohao1020/docs-cockpit/use-docs-cockpit"><img src="https://agentmods.dev/badge/skills/guohao1020/docs-cockpit/use-docs-cockpit/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/guohao1020/docs-cockpit/use-docs-cockpit"><img src="https://agentmods.dev/badge/skills/guohao1020/docs-cockpit/use-docs-cockpit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00098 | $0.00676 |
| Opus 5 | $0.00049 | $0.00338 |
| Sonnet 5 | $0.00020 | $0.00135 |
| Haiku 4.5 | $0.00010 | $0.00068 |
Grade A, and why
use-docs-cockpit 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 10d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
use-docs-cockpit
[Session context · docs-cockpit router] This block is injected at session start in any project with a
docs-cockpit.yaml. Its only job: route you to the right skill before you act on any docs-cockpit-related intent.
This project manages its documentation association system (module ↔ subtask ↔ spec/plan/RFC anchors) with docs-cockpit. North-star: cognition lives in skills, Python only renders — and anchor precision comes first: a wrong anchor is worse than a missing anchor.
This file is a router only. Each routed skill carries its own complete workflow — read it before acting; do not improvise doc-association work from here.
Routing
| You want to | Use | Trigger examples |
|---|---|---|
| Build or extend the association system — set up the cockpit itself (config + scan dirs + debug build issues), plan the whole project's spec/plan, wire modules to docs, fill anchor gaps (0→1 / whole-project) | docs-cockpit-build skill |
「把项目做成看板」「把文档体系建起来」「关联模块和文档」「规划 spec」 |
| Refresh an EXISTING association that drifted — anchors stale after refactor, spec evolved and links need re-sync | docs-cockpit-rebuild skill |
「关联乱了重新梳理」「anchor 失效了」 |
| Just regenerate the dashboard HTML, no association work | CLI docs-cockpit render |
「重新生成 dashboard」 |
| Read status / progress / blockers, no file changes | docs-cockpit-rebuild Phase 1 (pure status queries end there) |
「项目进度怎么样」「哪些卡了」 |
| Run a project health checkup / 健康检查 (existing cockpit — the report feeds the dashboard health panel) | docs-cockpit-rebuild skill |
「体检一下」 "run a health check" |
| Upgrade docs-cockpit itself | CLI docs-cockpit upgrade (see references/operations.md · upgrade) |
「升级 docs-cockpit」 "update docs-cockpit" |
Discriminator between the two skills: build = the association does not exist yet (or whole-project planning); rebuild = it already exists and needs diagnosis / refresh (or just reading).
When NOT to apply
If the project has no docs-cockpit.yaml at the repo root, this router does not apply — the project does not use docs-cockpit. (The SessionStart hook injects this file conditionally, but a marketplace install can also trigger it directly; check for the config first.)
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.
- 10d ago First seen · 31 lines · 98 tokens per session scan A d6b948dc6360
use-docs-cockpit is a skill published in the GitHub repository Guohao1020/docs-cockpit (2 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 676 once invoked, about $0.0005 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.