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 consul-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/consul-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/consul-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/consul-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/consul-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/consul-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.00012 | $0.02342 |
| Opus 5.5 | $0.00005 | $0.00937 |
| Sonnet 5.5 | $0.00002 | $0.00468 |
| Haiku 4.5 | $0.00001 | $0.00234 |
Grade A, and why
consul-knowledge-patch scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "X-Consul-Token: $CONSUL_HTTP_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HashiCorp Consul
Use this skill when designing, configuring, upgrading, or troubleshooting Consul deployments whose behavior depends on recent discovery, service-mesh, gateway, Kubernetes, security, Enterprise, or operational changes.
Treat the reference files as task-oriented supplements. Inspect the deployment's actual Consul and Envoy versions, edition, platform, topology, and configuration before applying guidance. Release-specific behavior does not replace an existing tested constraint.
Reference index
| Reference | Topics |
|---|---|
| Discovery, networking, and mesh | ESM, sessions, multi-port services, IPv6, Envoy compatibility, mesh routing, passive health |
| Enterprise operations and telemetry | support policy, utilization, RPC limits, HTTP timeouts, product and certificate telemetry, IBM licensing |
| Gateways, security, and identity | OIDC, KV validation, path normalization, SDS, gateway limits, CA providers, request limits, headers |
| Kubernetes and snapshots | GCS and Azure snapshots, Pod Security Admission, OpenShift, API Gateway scaling and migration |
| Upgrades and rollouts | license sequencing, maintained-version cadence, federated rollouts, protocol transitions, Autopilot |
Start with compatibility and security changes
Validate KV names before rollout
The KV endpoint rejects invalid key names by default. Audit writers and stored keys before upgrading. Use DisableKVKeyValidation only as a deliberate compatibility escape hatch, with a plan to remove invalid names.
Keep HTTP paths normalized before L7 authorization
API Gateway and terminating-gateway HTTP listeners normalize paths before intention RBAC checks. Custom envoy_public_listener_json HTTP Connection Manager filter chains receive the same normalization. Do not set InsecureDisablePathNormalization unless the bypass risk is explicitly accepted.
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 · 173 lines · 12 tokens per session scan A ba04cd973b7d
consul-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 2,342 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
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-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
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-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.