deno-knowledge-patch

deno-knowledge-patch is a skill for Claude Code from Nevaberry/nevaberry-plugins. It costs 9 tokens per session (3,046 once invoked), scanned A, original, MIT.

A reference guide for current Deno runtime APIs, command-line options, dependencies, Node compatibility, and deployment. Deno is a JavaScript and TypeScript runtime and toolset.

In plain words
What is it for?
Use it before changing a Deno project, then check the version, configuration, dependencies, permissions, code, tests, and build or deployment commands.
Why use it?
Deno commands and defaults can change between versions, so it helps prevent outdated instructions and incomplete manifest or lockfile updates.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the knowledge-patch plugin — 57 skills, 1 hook shipped together

Good fit Use it before changing a Deno project, then check the version, configuration, dependencies, permissions, code, tests, and build or deployment commands.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nevaberry/nevaberry-plugins/deno-knowledge-patch
Install

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.

Any agent
npx skills add Nevaberry/nevaberry-plugins --skill deno-knowledge-patch
Clone the repo
git clone --depth 1 https://github.com/Nevaberry/nevaberry-plugins

Made for: Claude Code.

Or install knowledge-patch, the plugin that ships this one along with the rest of its 57 skills, 1 hook.

Wrote 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.

agentmods badge for deno-knowledge-patch

README.md
[![agentmods](https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/deno-knowledge-patch/github.svg)](https://agentmods.dev/skills/nevaberry/nevaberry-plugins/deno-knowledge-patch)
Your own site
<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/deno-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/deno-knowledge-patch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for deno-knowledge-patch

Your own site · 80×15
<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/deno-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/deno-knowledge-patch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,046 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 110
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.03046
Opus 5.5 $0.00004 $0.01218
Sonnet 5.5 $0.00002 $0.00609
Haiku 4.5 $0.00001 $0.00305

Measured 1mo ago against content hash 16c6ba75ffc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deno-knowledge-patch 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 1mo 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.

plugins/knowledge-patch/patches-claude/deno-knowledge-patch/SKILL.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deno Knowledge Patch

Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.

Working approach

  1. Inspect deno --version, deno.json or deno.jsonc, package.json, deno.lock, workspace files, and CI commands.
  2. Read every reference relevant to the requested change; later version-attributed guidance supersedes earlier behavior only where it explicitly changes it.
  3. Preserve least-privilege permissions. Do not add -A merely to silence a permission failure.
  4. Keep manifest and lockfile changes together, and prefer frozen installation modes in CI.
  5. Treat the project's manifests, code, tests, and observed behavior as authoritative when they conflict with general guidance.
  6. Verify with the narrowest applicable built-ins: deno check, deno lint, deno fmt --check, deno test, and the requested build or package command.

Reference index

Reference Topics
Build, publish, and deploy Compilation, bundling, transpilation, packaging, publication, and deployment
Dependencies and workspaces Manifests, registries, npm and JSR resolution, lockfiles, installs, catalogs, and workspaces
Desktop and ecosystem Desktop applications, notebooks, Fresh, Deploy, Sandbox, and registry consumers
Deno 2 migration Removed surfaces, stricter checks, changed output, and changed defaults
Networking and observability HTTP, sockets, TLS, WebSockets, QUIC, inspectors, profiles, and OpenTelemetry
Node compatibility CommonJS, Node APIs, timers, workers, IPC, SQLite, tests, and diagnostics
Permissions and security Permission sets, allow and deny precedence, audit logs, scripts, and supply-chain policy
Runtime and Web APIs Files, subprocesses, WebAssembly, Temporal, cryptography, graphics, and Web APIs
Testing, linting, and formatting Tests, snapshots, retries, sharding, coverage, benchmarks, lint plugins, and formatters
Tooling and editor Type checking, TypeScript configuration, tasks, caching, CLI workflows, upgrades, and language-server behavior

Read the full file on GitHub · 226 lines

Changes

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.

  1. 1mo ago First seen · 226 lines · 9 tokens per session scan A 16c6ba75ffc2

Subscribe to this mod's changes

deno-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 3,046 once invoked, about $0.0000 per session on Opus 5.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.