Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/c9r-io/orchestrator/main/.claude/skills/guide-alignment/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/guide-alignment)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/guide-alignment"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/guide-alignment/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/c9r-io/orchestrator/guide-alignment"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/guide-alignment.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.00082 | $0.00873 |
| Opus 5.5 | $0.00033 | $0.00349 |
| Sonnet 5.5 | $0.00016 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
guide-alignment 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 2mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide Alignment
Since FR-154, CLI-vs-documentation drift is detected mechanically — this
skill is the repair procedure, not the detector. The single source of truth is
the clap tree, projected into config/governance/cli-surface.json; three
surfaces are held to it in CI:
| Surface | Enforced by | Where it runs |
|---|---|---|
config/governance/cli-surface.json freshness |
cli_surface_json_is_fresh (cargo test) |
test job |
built-in guide (crates/cli/src/commands/guide.rs) |
guide_matches_clap_leaves (cargo test) + gate check 5 |
test + governance jobs |
docs/guide/07-cli-reference.md EN + ZH |
scripts/qa/test-cli-doc-parity.sh (ci-required) |
governance job |
Procedure
-
Regenerate the surface after any
crates/cli/src/cli.rschange:ORCHESTRATOR_WRITE_CLI_SURFACE=1 cargo test -p orchestrator-cli cli_surface_json_is_freshRead the diff of
config/governance/cli-surface.json— it names exactly what changed (new paths, flags, defaults, hidden markers). -
Run the detector and read its diagnostics — never re-derive the drift by hand:
bash scripts/qa/test-cli-doc-parity.sh cargo test -p orchestrator-cli guide_matches_clap_leavesThe gate prints the missing paths per document, invalid/hidden invocations, and the two-sided guide-vs-surface diff.
-
Fix the built-in guide first: add/remove
GuideEntryitems incrates/cli/src/commands/guide.rs(command_entries(); pseudo-topics live separately intopic_entries()). Summaries come from theaboutstrings incli-surface.json; examples must use real flags with real defaults. -
Fix the markdown references:
docs/guide/07-cli-reference.md, then its structural mirrordocs/guide/zh/07-cli-reference.md. Coverage counts an inline backtick span or a fenced-code-block line that starts with the command path; HTML-commented mentions do not count. Follow the existing section layout; flags in tables, examples in ```bash blocks.
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.
- 2mo ago First seen · 73 lines · 82 tokens per session scan A a66ebc3ea301
guide-alignment is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 873 once invoked, about $0.0003 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.
Other skills, from other repositories
developing-openrig
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not…
dos-self-improve
Run the DOS self-improvement loop: propose a candidate, verify it in an isolated worktree, measure suite/truth/metric gates, and keep only confirmed gains. Use for recursive improvement; use dos-enforce-tune for policy knobs.
fix
Diagnose and fix a bug in an isolated git worktree with reproduce-first, test-first methodology.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
rust-check
Run cargo check on the current Rust project to find compile errors.