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 skills add akiojin/skills --skill skills-repo-maintenancegit clone --depth 1 https://github.com/akiojin/skillsWrote 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/akiojin/skills/skills-repo-maintenance)<a href="https://agentmods.dev/skills/akiojin/skills/skills-repo-maintenance"><img src="https://agentmods.dev/badge/skills/akiojin/skills/skills-repo-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.
<a href="https://agentmods.dev/skills/akiojin/skills/skills-repo-maintenance"><img src="https://agentmods.dev/badge/skills/akiojin/skills/skills-repo-maintenance.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00053 | $0.00787 |
| Opus 5 | $0.00026 | $0.00394 |
| Sonnet 5 | $0.00011 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
skills-repo-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 12d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Repo Maintenance
Overview
Maintain a skills repository and keep Codex and Claude Code artifacts in sync.
Workflow
0) Defaults to apply
- Target runtime: Codex + Claude Code (both).
- Package output: must be specified by the user every time (no default).
1) Identify the repo root
- Use the current repo (git root) as the base.
- Example:
git rev-parse --show-toplevel
2) Decide the target runtime(s)
- Default is both. If the user explicitly asks for only one runtime, confirm before skipping the other.
- Codex: add a skill folder with
SKILL.mdat repo root. - Claude Code: add a plugin folder with
.claude-plugin/plugin.jsonand update.claude-plugin/marketplace.json.- For both, do both and package
.skillfiles for Codex distribution.
- For both, do both and package
3) Create or update the skill content
- Skill folder must contain
SKILL.mdwith YAML frontmatter (name,description). - Use lowercase + hyphens for skill names.
- Put extra materials under
references/,scripts/,assets/as needed.
4) Claude Code plugin requirements (if applicable)
- Plugin lives at repo root (e.g.
drawio/,gh-fix-ci/,cli-design/). - Add
.claude-plugin/plugin.jsoninside the plugin folder. - Add an entry to
<repo-root>/.claude-plugin/marketplace.json:name,source,description,version,category,keywords
- If the plugin contains multiple skills, place them under
<plugin>/skills/<skill-name>/SKILL.md.
5) Codex packaging (if applicable)
- Package to the user-specified output directory using the skill packager.
- On Windows, set UTF-8 to avoid decode errors.
$env:PYTHONUTF8=1
$codexHome = $env:CODEX_HOME
if (-not $codexHome) { $codexHome = "$env:USERPROFILE\.codex" }
$outDir = "<output-dir>"
python "$codexHome\skills\.system\skill-creator\scripts\package_skill.py" `
"<repo-root>\\<skill-folder>" `
$outDir
export PYTHONUTF8=1
codex_home="${CODEX_HOME:-$HOME/.codex}"
out_dir="<output-dir>"
python "$codex_home/skills/.system/skill-creator/scripts/package_skill.py" \
"<repo-root>/<skill-folder>" \
"$out_dir"
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.
- 12d ago First seen · 87 lines · 53 tokens per session scan A c29d5c2067ea
skills-repo-maintenance is a skill published in the GitHub repository akiojin/skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 787 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…