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/dojogenesis/mcp/skill-maintenancenpx skills add DojoGenesis/mcp --skill skill-maintenancegit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/skill-maintenance)<a href="https://agentmods.dev/skills/dojogenesis/mcp/skill-maintenance"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/skill-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.00054 | $0.02782 |
| Opus 5 | $0.00027 | $0.01391 |
| Sonnet 5 | $0.00011 | $0.00556 |
| Haiku 4.5 | $0.00005 | $0.00278 |
Grade A, and why
skill-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 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.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Maintenance
I. Philosophy: Maintenance Is Keeping What Works Working Well
A skills directory is a living knowledge base. As the project evolves, skill names may become unclear, terminology may need updating, and cross-references may drift out of sync. Without systematic maintenance, the knowledge base degrades: skills become hard to find, references break, and terminology becomes inconsistent.
This skill transforms maintenance from a reactive chore into a proactive ritual. By following a structured process -- read, check, propose, execute, verify, document -- we ensure the skills directory remains clear, consistent, and valuable.
Good maintenance prevents future problems. A well-maintained knowledge base is easier to search, easier to understand, and easier to extend.
II. When to Use This Skill
- Skill names become unclear or outdated -- names no longer describe what the skill does
- Terminology needs updating -- tool-specific language should be generalized, or industry terms have shifted
- Adding new skills -- new skills reference existing skills and need cross-reference validation
- Deprecating or merging skills -- old skills need to be removed or consolidated
- Conducting periodic audits -- regular health checks (quarterly recommended)
- After a major refactor -- ensuring consistency after large-scale changes
- Onboarding new contributors -- ensuring the knowledge base is accessible
When NOT to use: For creating new skills (use skill-creation). For ecosystem-wide assessment (use skill-audit). This skill is for maintaining individual skills or small groups.
III. The Maintenance Workflow
Step 1: Recognize the Need
Goal: Identify when maintenance is needed and clarify scope.
Actions:
- Identify the trigger: user request, noticed inconsistency, scheduled audit, or new skill addition
- Clarify scope with the user: What specifically needs to change? What should stay the same?
- Document the maintenance goal
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 · 326 lines · 54 tokens per session scan A 94e2c88d45a4
skill-maintenance is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 2,782 once invoked, about $0.0003 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.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
prune-npm-overrides
Audit the pnpm overrides a repo already carries, remove the ones upstream has since fixed, and require a justification comment on every one that stays. The counterpart to fix-npm-vulnerability. Use when asked to check, clean up, or prune the overrides, or when an override's tracking issue comes up for review.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.