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/cyanheads/git-mcp-server/maintenancenpx skills add cyanheads/git-mcp-server --skill maintenancegit clone --depth 1 https://github.com/cyanheads/git-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/cyanheads/git-mcp-server/maintenance)<a href="https://agentmods.dev/skills/cyanheads/git-mcp-server/maintenance"><img src="https://agentmods.dev/badge/skills/cyanheads/git-mcp-server/maintenance.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.00053 | $0.01244 |
| Opus 5 | $0.00026 | $0.00622 |
| Sonnet 5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
maintenance 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use `WebFetch` or `Bash + curl` (for full content) against the package's GitHub releases or CHANGELOG. Skim tag-to-tag diffs rather than scrolling the full file. How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- After running
bun update --latestyourself and wanting to review the impact (Mode B — typical) - To run the whole flow end-to-end — outdated check → update → investigate → adopt → verify (Mode A)
Entry Modes
| Mode | Starting Point | First Step |
|---|---|---|
| A — Full flow | Lockfile is current; want to update | Step 1 |
| B — Post-update review | User already ran bun update --latest + bun run rebuild + bun test |
Skip to Step 3 with the update output or git diff bun.lock |
Both modes converge at Step 3 and end at Step 6.
Steps
1. Survey what's outdated (Mode A only)
bun outdated
Note: bun update --latest crosses semver majors; bun update alone respects ranges. Use --latest unless a package is intentionally pinned.
2. Apply the update (Mode A only)
bun update --latest
Capture the ↑ package old → new lines from stdout — these feed Step 3. Alternatively, git diff bun.lock surfaces version deltas after the fact.
3. Investigate changelogs
For each updated package, fetch the release notes or CHANGELOG entries between old and new versions, then cross-reference changes against actual imports in src/. Output per package: what changed, impact on this project, action items.
Focus on packages this server directly depends on:
| Package | Impact Check |
|---|---|
@modelcontextprotocol/sdk |
Protocol version bumps, breaking handler signatures, new capabilities |
hono / @hono/node-server / @hono/mcp |
HTTP transport API changes, middleware signatures |
@opentelemetry/* |
Instrumentation contract changes, exporter config |
tsyringe / reflect-metadata |
DI container behavior, decorator semantics |
jose |
JWT/JWKS verification API |
pino / pino-pretty |
Logger API, transport config |
zod |
Schema API (e.g., v3 → v4 refinement changes, .describe() behavior) |
typescript |
New strict checks, lib changes affecting existing types |
vitest / @vitest/coverage-v8 |
Test runner behavior, coverage provider changes |
eslint / typescript-eslint |
New rules flagging existing code |
| Cross-spawn / execa | Child-process spawning semantics used by CliGitProvider |
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 · 116 lines · 53 tokens per session scan A 4f7780533418
maintenance is a skill published in the GitHub repository cyanheads/git-mcp-server (239 stars, last pushed 10d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,244 once invoked, about $0.0003 per session on Opus 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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
quick-capture
Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.
xmemo-vscode
Use XMemo from VS Code (and forks like Cursor/Windsurf) to recall project context, capture engineering decisions, preserve handoff state, and connect to the hosted XMemo MCP endpoint safely.
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
freshness-check
Model-aware staleness check before asserting how a PoE mechanic/item/system works, plus a scope filter so league/event mechanics don't bleed into the wrong character. Routes to freshnessindex.md + mechanicsindex.md.
mcp2cli
Use mcp2cli to connect to, explore, and execute commands against any MCP (Model Context Protocol) server from the terminal. Covers discovery, tool invocation, resource reading, prompt execution, alias creation, config management, background jobs, authentication, and JSON output pipelines.