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/nevaberry/nevaberry-plugins/deno-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill deno-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/deno-knowledge-patch)<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="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.00009 | $0.03046 |
| Opus 5 | $0.00005 | $0.01523 |
| Sonnet 5 | $0.00002 | $0.00609 |
| Haiku 4.5 | $0.00001 | $0.00305 |
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 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.
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
- Inspect
deno --version,deno.jsonordeno.jsonc,package.json,deno.lock, workspace files, and CI commands. - Read every reference relevant to the requested change; later version-attributed guidance supersedes earlier behavior only where it explicitly changes it.
- Preserve least-privilege permissions. Do not add
-Amerely to silence a permission failure. - Keep manifest and lockfile changes together, and prefer frozen installation modes in CI.
- Treat the project's manifests, code, tests, and observed behavior as authoritative when they conflict with general guidance.
- 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 |
What ships with it
11 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.
- coverage.json 2.4 KB
- references/build-publish-and-deploy.md 8.0 KB
- references/dependencies-and-workspaces.md 12 KB
- references/desktop-and-ecosystem.md 5.0 KB
- references/migration.md 5.2 KB
- references/networking-and-observability.md 8.6 KB
- references/node-compatibility.md 17 KB
- references/permissions-and-security.md 7.3 KB
- references/runtime-and-web-apis.md 14 KB
- references/testing-lint-and-format.md 12 KB
- references/tooling-and-editor.md 12 KB
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 · 226 lines · 9 tokens per session scan A 16c6ba75ffc2
deno-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 3,046 once invoked, about $0.0000 per session on Opus 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.
Other skills, from other repositories
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.