A maintenance procedure for keeping project skills and agent skill folders aligned with the skills supplied by a software package.

It checks versions, copies new or updated external skills into the project, and synchronizes them with the agent’s skill directory.

Package updates can leave project and agent instructions out of sync, causing agents to use missing or outdated skills.

maintenance — Skill for Claude Code and Codex by magnusquest

Install

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.

Any agent

npx skills add magnusquest/startgg-mcp --skill maintenance

Clone the repo

git clone --depth 1 https://github.com/magnusquest/startgg-mcp

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/magnusquest/startgg-mcp/maintenance/github.svg)](https://agentmods.dev/skills/magnusquest/startgg-mcp/maintenance)

Your own site

<a href="https://agentmods.dev/skills/magnusquest/startgg-mcp/maintenance"><img src="https://agentmods.dev/badge/skills/magnusquest/startgg-mcp/maintenance/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/magnusquest/startgg-mcp/maintenance"><img src="https://agentmods.dev/badge/skills/magnusquest/startgg-mcp/maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 572 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00044	$0.00572
Opus 5	$0.00022	$0.00286
Sonnet 5	$0.00009	$0.00114
Haiku 4.5	$0.00004	$0.00057

Measured 9d ago against content hash 27436eb78eb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

maintenance 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 9d 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.

skills/maintenance/SKILL.md · 56 lines

What it actually says

Context

Skills flow through three tiers:

Package — node_modules/@cyanheads/mcp-ts-core/skills/ (canonical source)
Project — skills/ at project root (source of truth for this project)
Agent — your agent skill directory (e.g., .claude/skills/)

After bun update @cyanheads/mcp-ts-core, Tier 1 may have newer skills than Tier 2, and Tier 3 may be out of sync with Tier 2 at any time.

Steps

Sync project skills (Tier 1 → Tier 2)

List all skill directories in node_modules/@cyanheads/mcp-ts-core/skills/
For each skill with metadata.audience: external in its SKILL.md frontmatter:
- If the skill does not exist in project skills/, copy the full directory
- If it exists, compare metadata.version — if the package version is newer, replace the full directory
- If the local version is equal or newer, skip (local override)
Do not touch skills in skills/ that don't exist in the package (server-specific)

Sync agent skills (Tier 2 → Tier 3)

Compare your agent skill directory against project skills/
Copy any missing skills from skills/ to your agent directory
For existing skills, compare file contents — update if skills/ is newer
Do not remove skills from your agent directory that aren't in skills/

Dependency updates

Run bun outdated to see what's out of date
Review changelogs for any major version bumps before proceeding
Run bun update to update dependencies
Run bun audit to check for vulnerabilities introduced by the update
Run bun run devcheck to confirm lint, types, and tests still pass

Checklist

Package skills compared against project skills/ (version check)
New or updated skills copied to project skills/
Agent skill directory in sync with project skills/
Dependencies updated (bun update)
bun audit passes (no new vulnerabilities)
bun run devcheck passes

Changes

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.

9d ago First seen · 56 lines · 44 tokens per session scan A 27436eb78eb6

Subscribe to this mod's changes

maintenance is a skill published in the GitHub repository magnusquest/startgg-mcp (1 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 572 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-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens