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/cintia09/codenook/install-orchestratornpx skills add cintia09/CodeNook --skill install-orchestratorgit clone --depth 1 https://github.com/cintia09/CodeNookWrote 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/cintia09/codenook/install-orchestrator)<a href="https://agentmods.dev/skills/cintia09/codenook/install-orchestrator"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/install-orchestrator.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.00000 | $0.00568 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
install-orchestrator 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 4d 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.
What it actually says
install-orchestrator — runs the 12-gate plugin install pipeline
This skill is the heart of M2. It takes a staged plugin source
(directory or tarball) and runs 12 gates in fixed order before
atomically moving the plugin into
<workspace>/.codenook/plugins/<id>/.
Gate order
| # | code | gate skill / inline | failure → exit |
|---|---|---|---|
| 1 | G01 | plugin-format | 1 |
| 2 | G02 | plugin-schema | 1 |
| 3 | G03 | plugin-id-validate | 3 if "already installed", else 1 |
| 4 | G04 | plugin-version-check | 1 |
| 5 | G05 | plugin-signature | 1 |
| 6 | G06 | plugin-deps-check | 1 |
| 7 | G07 | plugin-subsystem-claim | 1 |
| 8 | G08 | sec-audit (subprocess) | 1 |
| 9 | G09 | inline size check (≤10MB total, ≤1MB each) | 1 |
| 10 | G10 | plugin-shebang-scan | 1 |
| 11 | G11 | plugin-path-normalize | 1 |
| 12 | G12 | inline atomic commit + state.json append | 1 |
CLI
orchestrator.sh --src <tarball|dir> --workspace <dir>
[--upgrade] [--dry-run] [--json]
The top-level install.sh is just a thin wrapper that calls this.
Stage / commit lifecycle
- Stage — copy/extract
--srcinto<workspace>/.codenook/staging/<random>/(created on demand). - Run gates — each gate skill is invoked as a subprocess with
--json; the orchestrator collects{ok, gate, reasons}records. - Decide — on any failure: print reasons (
[Gxx] ...), keep the staging dir (so the user can inspect it), and exit non-zero. - Commit — on full pass and not
--dry-run: atomicos.replace()of the staging dir to<workspace>/.codenook/plugins/<id>/, then append a record to<workspace>/.codenook/state.json(.installed_plugins[]) using_lib/atomic.atomic_write_json. - Cleanup — after a successful commit, remove the staging parent if empty.
What ships with it
2 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.
- 4d ago First seen · 49 lines · 0 tokens per session scan A e0f34b9f6773
install-orchestrator is a skill published in the GitHub repository cintia09/CodeNook (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 568 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…