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-validatenpx skills add cintia09/CodeNook --skill config-validategit clone --depth 1 https://github.com/cintia09/CodeNookWhat 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.00399 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
config-validate 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 2d 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
config-validate (builtin skill)
Role
Field-level validator for merged CodeNook configs (output of config-resolve).
Checks types, ranges, enums; emits warnings for deprecated keys. Separate
from config-resolve's top-key whitelist (which is about routing only).
CLI
validate.sh --config <merged.json> [--schema <config-schema.yaml>] [--json]
--configrequired; must be valid JSON object.--schemadefaults to the packagedconfig-schema.yamlshipped alongside this SKILL.--jsonswitches stdout to{ ok, errors, warnings }(stderr still carries human-readable lines).
Exit codes
| code | meaning |
|---|---|
| 0 | no errors (warnings permitted) |
| 1 | at least one validation error |
| 2 | usage error (missing/bad flags, missing files) |
Error shape (--json)
{
"ok": false,
"errors": [{ "path": "models.default", "msg": "must be at least 1 char(s)" }],
"warnings": [{ "path": "legacy_router", "msg": "deprecated key" }]
}
Schema DSL
See config-schema.yaml header comments. Supports string|integer|object,
required, min_length, min, enum, nested fields. Unknown top-level
keys are tolerated (routing-layer decides those); only entries in the
schema's deprecated: list emit warnings.
Notes
- M1 scope: enough coverage for DoD fields (
models.default,hitl.mode,concurrency.max_parallel). Grow the schema as subsystems land. - M5 will layer plugin-specific schemas on top (see implementation.md §M5.2).
What ships with it
3 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.
- 2d ago First seen · 52 lines · 0 tokens per session scan A 9f07c6fd8434
config-validate 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 399 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…