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/mcpc-tech/mcpc/version-upgradenpx skills add mcpc-tech/mcpc --skill version-upgradegit clone --depth 1 https://github.com/mcpc-tech/mcpcWrote 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/mcpc-tech/mcpc/version-upgrade)<a href="https://agentmods.dev/skills/mcpc-tech/mcpc/version-upgrade"><img src="https://agentmods.dev/badge/skills/mcpc-tech/mcpc/version-upgrade.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.00033 | $0.00423 |
| Opus 5 | $0.00016 | $0.00211 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
version-upgrade 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.
What it actually says
Version Upgrade Skill
Upgrade mcpc package versions and their dependencies.
When to Use
User asks to upgrade versions, like:
- "upgrade core version"
- "upgrade all packages"
- "bump versions"
Steps
1. Read Current Versions
Read each packages/*/deno.json to find current versions.
- Core is the base - upgrade it first
- Other packages depend on core
2. Increment Version
For each package:
- Increment the appropriate segment (patch/minor/major)
- Match the pattern: if core goes 0.3.38 → 0.3.39, dependents should reference ^0.3.39
3. Sync CLI Version
If CLI is updated:
- Find
CLI_VERSIONinpackages/cli/src/config/loader.ts - Update to match cli deno.json version
4. Verify
deno lint
deno test --allow-all packages/*/tests/
Version Patterns
| Type | Pattern | When |
|---|---|---|
| Core | 0.3.x | Feature additions |
| CLI | 0.1.x | Feature additions |
| Utils | 0.2.x | Feature additions |
| Plugins | 0.0.x | Patch=fix, Minor=feature |
Key Files to Update
packages/core/deno.json- base versionpackages/*/deno.json- each package's version + core dependencypackages/cli/src/config/loader.ts- CLI_VERSION constant
Tips
- Always upgrade core first, then dependents
- Check for dependency warnings with
deno lint - Update CLI_VERSION to match deno.json version
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 · 69 lines · 33 tokens per session scan A 8be183ce3a52
version-upgrade is a skill published in the GitHub repository mcpc-tech/mcpc (104 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 423 once invoked, about $0.0002 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
mcp-google-map-project
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.
authoring-decorators
Use when the user wants to write a new prompt decorator - either a personal one for their repo or a contribution back to the upstream catalogue. Walks through the JSON schema, the extensions/ convention, how to verify a new decorator end-to-end through the hook, and how to diagnose failures using debug logging and…
arkana-analyse
British English alias for the arkana-analyze skill. Binary analysis skill for Arkana. Triggers on: analyse, analyze, binary, malware, reverse engineer.