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 skills add Nevaberry/nevaberry-plugins --skill debian-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/debian-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/debian-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/debian-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.
<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/debian-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/debian-knowledge-patch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00009 | $0.02035 |
| Opus 5.5 | $0.00004 | $0.00814 |
| Sonnet 5.5 | $0.00002 | $0.00407 |
| Haiku 4.5 | $0.00001 | $0.00203 |
Grade A, and why
debian-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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debian knowledge patch
Navigate the references
Choose references by the task at hand. Read every relevant file before changing an upgrade plan, package set, boot configuration, network configuration, or stateful service.
| Reference | Topics |
|---|---|
| packages-toolchains-desktops.md | Command and package replacements, component splits, desktop stacks, compatibility packages, and pending removals |
| release-platform.md | Architecture and ABI boundaries, platform defaults, hardware enablement, virtual machines, and support lifecycle |
| security-networking.md | Remote access, encrypted storage, sysctl, ping, interface naming, TLS, IPsec, and Secure Boot data |
| services-data.md | RabbitMQ, MariaDB, Dovecot, and Bacula migrations |
| upgrade-foundations.md | Preflight checks, sequencing, rollback planning, and post-upgrade verification |
Triage breaking upgrade risks first
Before approving an in-place upgrade, identify whether the host is:
- reached only through SSH;
- using a separate
/boot; - mounting encrypted filesystems, especially plain-mode dm-crypt;
- running RabbitMQ, MariaDB, Dovecot, or Bacula;
- dependent on stable network-interface names or
/etc/sysctl.conf; - using a retired architecture or third-party
armelorarmhfbinaries; - relying on custom WirePlumber, strongSwan, OpenLDAP, Samba, or libvirt setup;
- carrying packages or commands that no longer exist.
Treat each match as a required migration, verification, or rollback-planning step. Do not defer it to post-upgrade cleanup.
Protect remote access and bootability
Prepare SSH before a remote upgrade
- Install
openssh-serverversion1:9.2p1-2+deb12u7or later fromstable-updatesbefore starting an SSH-supervised upgrade. - Move variables required by SSH sessions out of
~/.pam_environment; new sessions no longer read it by default. - Replace DSA keys. OpenSSH 9.8p1 and later cannot re-enable them.
- Use
ssh1fromopenssh-client-ssh1only for devices that provide no other key type.
What ships with it
6 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.
- 1mo ago First seen · 188 lines · 9 tokens per session scan A 10c5f2d87d7b
debian-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 2,035 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.
Other skills, from other repositories
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
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…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…