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/ansible-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill ansible-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/ansible-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/ansible-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/ansible-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.00010 | $0.01982 |
| Opus 5 | $0.00005 | $0.00991 |
| Sonnet 5 | $0.00002 | $0.00396 |
| Haiku 4.5 | $0.00001 | $0.00198 |
Grade A, and why
ansible-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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ansible Core Knowledge Patch
Use this skill when changing Ansible playbooks, inventories, controller plugins,
connection settings, test targets, or modules that depend on current
ansible-core behavior.
Working Method
- Determine the installed or pinned
ansible-coreversion from dependency manifests, execution-environment definitions, or lockfiles. - Inspect the affected playbooks and plugins for the migration points below.
- Open the topic reference before changing behavior that depends on an exact configuration name, default, result type, or plugin API.
- Prefer project tests and observed runtime behavior when a project carries compatibility shims or backports.
Reference Index
| Reference | Topics |
|---|---|
| templating.md | Trust, single-pass evaluation, native values, strict conditionals, lazy templating, omit, sandboxing, and JSON profiles |
| plugins-and-extensions.md | Controller-side I/O, callback and strategy migrations, Jinja plugins, markers, builtin names, vars plugins, and collection packages |
| connections-and-privilege.md | SSH agents and askpass, Paramiko migration, connection verbosity, local become, and sudo_chdir |
| playbooks-cli-and-inventory.md | CLI flags, inventory parsing, diagnostics, deprecated play syntax, argument-spec validation, and Galaxy behavior |
| modules-facts-and-windows.md | Fact access, file and package modules, result types, UTF-8 enforcement, Windows execution, and module patch behavior |
| testing-runtime-and-security.md | ansible-test environments and timeout diagnostics, supported runtimes, maintenance dates, and security fixes |
Highest-Priority Migration Checks
Treat templating as trusted and single-pass
- Jinja expressions in untrusted strings, including facts and module results, are not evaluated merely because the strings contain delimiters.
- Preserve trust when a plugin transforms a value that is intended to remain a template. Apply trust explicitly when a plugin creates such a value.
- Remove designs that depend on one template producing another template for a later pass.
- Do not wrap ordinary conditionals in
{{ ... }}. A whole trusted string expression is the narrow exception.
What ships with it
7 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.
- 4d ago First seen · 213 lines · 10 tokens per session scan A 9235738c50d6
ansible-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 8d ago), licensed MIT. It adds 10 tokens to every session and 1,982 once invoked, about $0.0001 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-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.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-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.
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…
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.
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.