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/plugin-deps-checknpx skills add cintia09/CodeNook --skill plugin-deps-checkgit 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.00468 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
plugin-deps-check 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
plugin-deps-check — Install gate G06
Verifies the plugin's declared requires.core_version constraint
against the running core VERSION.
CLI
deps-check.sh --src <dir> [--core-version <v>] [--json]
If --core-version is omitted, the core VERSION file shipped with
this repo (skills/codenook-core/VERSION) is read.
Constraint syntax
Comma-separated comparator list (logical AND):
>=0.2.0,<1.0.0
>=0.2.0
==0.2.0
Supported operators: >=, <=, >, <, ==, =, !=. Operands
must be valid SemVer 2.0 strings.
⚠️ NOTE — SemVer pre-release precedence (M2 caveat)
Per SemVer §11.4, a version with a pre-release identifier has lower precedence than the same version without one:
0.2.0-m2.1 < 0.2.0-m2.2 < 0.2.0
While core is on 0.2.0-m2.x (M2 milestone pre-release), plugin authors
who want to require "M2 or newer" must spell their constraint with an
explicit pre-release floor — >=0.2.0 would reject every M2 build
because every M2 build sorts before 0.2.0.
# plugin.yaml — correct for M2-era plugins:
requires:
core_version: '>=0.2.0-m2' # ✅ accepts 0.2.0-m2.1, 0.2.0-m2.2, 0.2.0, ...
# plugin.yaml — WRONG during M2:
requires:
core_version: '>=0.2.0' # ❌ rejects every 0.2.0-m2.x build
Once core ships final 0.2.0, plain >=0.2.0 becomes correct.
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.
- 2d ago First seen · 54 lines · 0 tokens per session scan A a7643b764864
plugin-deps-check 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 468 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.