Borrowing it
Nothing to install: this file belongs to apollographql/apollo-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/apollographql/apollo-mcp-server/main/.agents/skills/mcp-apps-sync-docs/SKILL.mdgit clone --depth 1 https://github.com/apollographql/apollo-mcp-serverWrote 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/apollographql/apollo-mcp-server/mcp-apps-sync-docs)<a href="https://agentmods.dev/skills/apollographql/apollo-mcp-server/mcp-apps-sync-docs"><img src="https://agentmods.dev/badge/skills/apollographql/apollo-mcp-server/mcp-apps-sync-docs.svg" alt="Measured on agentmods" 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.00153 | $0.01146 |
| Opus 5 | $0.00077 | $0.00573 |
| Sonnet 5 | $0.00031 | $0.00229 |
| Haiku 4.5 | $0.00015 | $0.00115 |
Grade A, and why
mcp-apps-sync-docs 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill updates the MCP Apps documentation based on changes in the @apollo/client-ai-apps CHANGELOG from a specified version onward. It reads the changelog, compares it against the current docs, and makes targeted edits — without committing.
What you need from the user
One thing: a minimum version (e.g., 0.6.0 or v0.6.2). All changelog entries from that version to the latest will be analyzed.
Step 1: Fetch the changelog
Use the GitHub CLI to fetch the full changelog:
gh api repos/apollographql/apollo-client-ai-apps/contents/CHANGELOG.md --jq '.content' | base64 -d
Step 2: Parse relevant versions
The changelog uses this structure:
## 0.6.5 (2026-03-23)
### Features
#### Feature title
Description and code examples...
### Fixes
#### Fix title
Description...
Collect all version sections where the version number is greater than or equal to the user's minimum version. Ignore everything below that version. Parse each section into: version number, date, list of features, list of fixes, and any breaking changes or deprecations called out explicitly.
Step 3: Read the docs
Read all six documentation files. Understand what each one covers before analyzing the changelog:
docs/source/mcp-apps.mdx— MCP Apps overview: what are MCP apps, high-level overview, architecture diagramdocs/source/mcp-apps-architecture.mdx— How MCP Apps work: the discovery and tool execution phases, architecture diagramsdocs/source/mcp-apps-quickstart.mdx— Step-by-step setup guide using the Apollo AI Apps Template; Vite plugin behavior; project structuredocs/source/mcp-apps-development.mdx— Day-to-day development patterns, directives, hooks, and client usagedocs/source/mcp-apps-prerequisites.mdx— System and account prerequisites before buildingdocs/source/mcp-apps-reference.mdx— API reference: directives (@tool,@prefetch,@private), hooks (useToolInfo, etc.), manifest, configuration
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.
- 8d ago First seen · 101 lines · 153 tokens per session scan A e69da1b5bd71
mcp-apps-sync-docs is a skill published in the GitHub repository apollographql/apollo-mcp-server (308 stars, last pushed 2d ago), licensed MIT. It adds 153 tokens to every session and 1,146 once invoked, about $0.0008 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
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.
performing-graphql-introspection-attack
Performs GraphQL introspection attacks to extract the full API schema including types, queries, mutations, subscriptions, and field definitions from GraphQL endpoints. The tester uses introspection queries to map the attack surface, identifies sensitive fields and mutations, tests for query depth and complexity…
hunt-nestjs
Hunt NestJS-specific vulnerabilities: guard bypass, decorator gaps, and microservice auth drift.
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
nornicdb-knowledge-policies
Author and use NornicDB knowledge-layer policies (decay profiles, parameter bundles, promotion profiles, promotion policies) from Cypher. Use when writing CREATE/ALTER/DROP/SHOW DECAY PROFILE / PROMOTION PROFILE / PROMOTION POLICY, calling nornicdb.knowledgepolicy. procedures, or reading entity scores via decayScore()…