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.
git 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/commands/guohao1020/docs-cockpit/lint)<a href="https://agentmods.dev/commands/guohao1020/docs-cockpit/lint"><img src="https://agentmods.dev/badge/commands/guohao1020/docs-cockpit/lint.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.1 | $0.00016 | $0.00786 |
| Opus 5 | $0.00008 | $0.00393 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
lint 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 7d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explicit invocation of docs-cockpit lint — check every module / concept MD against the references/schema.md spec. Reports error (won't render at all) · warn (renders but UX problems) · hint (polish suggestions), each with a concrete fix + reference to the relevant schema section.
Why this command exists
docs-cockpit render writes HTML + emits validation issues. But sometimes you just want to know "is my frontmatter clean?" without rebuilding — e.g. before a commit, in CI, or when iterating on a single MD file. That's lint.
What this slash command does
When user invokes /docs-cockpit:lint:
- Run
docs-cockpit lintfrom project root (default config:docs-cockpit.yaml) - If exit code 0 + no output → confirm: "✓ All modules / concepts pass schema spec."
- If exit code 0 with hints → show hints, mention they're optional polish
- If exit code 1 (errors) → surface the structured output:
- For each
❌ errorblock: file · field · message · suggested fix ·📚 seereference - Group by file (a module with 3 issues groups as one block)
- Then offer: "Want me to fix these using the
docs-cockpit-buildskill (Phase 5-6: conversation + commit), or do you want to review them first?"
- For each
- Always end with the summary line: "X error(s) · Y warning(s) · Z hint(s) · reference: references/schema.md"
Argument handling
/docs-cockpit:lint(no args) → default · human-readable output/docs-cockpit:lint --json→ JSON output (for piping to CI / IDE)/docs-cockpit:lint --strict-warn→ upgrade warnings to errors (CI strict mode)/docs-cockpit:lint <path-to-yaml>→ use a non-default config
What you (Claude) should do with the output
The validator output is structured — each issue has 5 fields you should surface in order:
❌ <filename> · <field>: <message>
💡 fix: <suggestion>
📚 see: references/schema.md · <section>
Don't paraphrase these into vague advice — the precision is the point. The user can grep for the field name, look up the reference section, and fix once and forever.
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.
- 7d ago First seen · 53 lines · 16 tokens per session scan A 0b20be86256a
lint is a command published in the GitHub repository Guohao1020/docs-cockpit (2 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 786 once invoked, about $0.0001 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 commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.