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/config-resolvenpx skills add cintia09/CodeNook --skill config-resolvegit 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/config-resolve)<a href="https://agentmods.dev/skills/cintia09/codenook/config-resolve"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/config-resolve.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.00963 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
config-resolve 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
config-resolve (builtin skill)
Role
Sub-agent self-bootstrap helper: produce the effective config tree for
(plugin, task) by deep-merging the 4 declared layers + Layer 0 builtin
defaults, then expanding tier_* model symbols against the workspace's
model catalog. Called by sub-agents — never by main session.
Implements architecture §3.2.4 (4-layer config) + §3.2.4.1 (5-layer model chain + Router exception) + §3.2.4.2 (tier symbol expansion + provenance).
CLI
resolve.sh --plugin <name> --task <T-NNN> --workspace <path> [--catalog <path>]
--plugin __router__is the router sentinel: Layer 1 and Layer 3 are forced empty (Router exception per §3.2.4.1 / M-016).--taskis optional. When omitted, Layer 4 is empty.--catalogdefaults to<workspace>/.codenook/state.json(extracts.model_catalog). May point to a standalone JSON file with the same shape (used by tests).
Layers
| Layer | Source |
|---|---|
| 0 | Builtin: {"models": {"default": "tier_strong"}} |
| 1 | <ws>/.codenook/plugins/<plugin>/config-defaults.yaml |
| 2 | <ws>/.codenook/config.yaml → .defaults |
| 3 | <ws>/.codenook/config.yaml → .plugins.<plugin>.overrides |
| 4 | <ws>/.codenook/tasks/<task>/state.json → .config_overrides |
Output
JSON to stdout. Top-level merged config + a _provenance map keyed by
flat dotted leaf paths (e.g. "models.planner"):
{
"models": { "planner": "opus-4.7", "default": "opus-4.7" },
"_provenance": {
"models.planner": {
"value": "opus-4.7",
"from_layer": 1,
"symbol": "tier_strong",
"resolved_via": "model_catalog.resolved_tiers.strong"
}
}
}
Tier expansion (step 5)
After deep-merge, walk every models.* value:
- Starts with
tier_and tier ∈ {strong, balanced, cheap}: look up incatalog.resolved_tiers[tier]. If null → fallback chainstrong → balanced → cheap. If all null → hardcodedopus-4.7,resolved_via = "fallback:hardcoded". - Starts with
tier_<other>: warn to stderr, fallback totier_strong,resolved_via = "fallback:tier_strong". - Literal (no
tier_prefix): passthrough;resolved_via = "literal",symbol = null. (Catalog membership not enforced in M1.)
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.
- 3d ago First seen · 91 lines · 0 tokens per session scan A c1ef11bae741
config-resolve 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 963 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…