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/apollo-graphql-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill apollo-graphql-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/apollo-graphql-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/apollo-graphql-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/apollo-graphql-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.00011 | $0.02734 |
| Opus 5 | $0.00005 | $0.01367 |
| Sonnet 5 | $0.00002 | $0.00547 |
| Haiku 4.5 | $0.00001 | $0.00273 |
Grade A, and why
apollo-graphql-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 3d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apollo GraphQL Knowledge Patch
Use this skill when work involves recent Apollo Client, Apollo Server, Apollo Router, or Apollo Connectors behavior. Identify the product and installed version first, then read only the relevant topic reference.
Reference index
| Reference | Topics |
|---|---|
| client-data-and-cache.md | Query and mutation lifecycles, fragments, cache writes, local state, mocks, refetch events |
| client-migration.md | Client 4 migration, packages, links, errors, RxJS, incremental delivery, SSR, modern typing |
| router-caching-and-traffic.md | Backpressure, traffic shaping, persisted queries, Redis, response/entity caches, subscriptions |
| router-connectors-and-extensions.md | Connector schemas and transport, coprocessors, Rhai, Rust plugins |
| router-execution-and-delivery.md | Query planning, demand control, response validation, error paths, deferred delivery |
| router-migration-and-security.md | Router upgrades, configuration, JWT, CORS, HTTP hardening, deployment, reloads |
| router-observability.md | Metrics, selectors, spans, errors, exporters, cardinality, sampling |
| server.md | Server 5 runtime, integrations, proxying, incremental protocols, execution limits, HTTP hardening |
Apply this patch
- Determine whether the task concerns Client, Server, Router, Connectors, or an integration between them.
- Read the project's manifest and lockfile to identify exact product versions before applying version-gated advice.
- For upgrades, preserve the intermediate migrations described below and in the product reference; do not jump straight to renamed configuration.
- For Router changes, check security, traffic, and telemetry defaults together because one upgrade can affect status codes, load shedding, and dashboards.
- For incremental delivery, align the Client handler, Server GraphQL.js alpha, and
Acceptprotocol exactly. - Preserve explicit compatibility overrides unless the task authorizes their removal.
What ships with it
9 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 3.3 KB
- references/client-data-and-cache.md 7.5 KB
- references/client-migration.md 9.6 KB
- references/router-caching-and-traffic.md 12 KB
- references/router-connectors-and-extensions.md 9.2 KB
- references/router-execution-and-delivery.md 4.4 KB
- references/router-migration-and-security.md 12 KB
- references/router-observability.md 17 KB
- references/server.md 5.0 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.
- 3d ago First seen · 180 lines · 11 tokens per session scan A 4f52f65fe8da
apollo-graphql-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 2,734 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
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-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
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-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.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…