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/c9r-io/orchestrator/guide-alignmentnpx skills add c9r-io/orchestrator --skill guide-alignmentgit 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.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.00082 | $0.00873 |
| Opus 5 | $0.00041 | $0.00436 |
| Sonnet 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 5d 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.
- 5d 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 3d ago), licensed MIT. It adds 82 tokens to every session and 873 once invoked, about $0.0004 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-30.
Other skills, from other repositories
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…