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/rdudov/task-agent/skill-maintainernpx skills add rdudov/task-agent --skill skill-maintainergit clone --depth 1 https://github.com/rdudov/task-agentWhat 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.00040 | $0.00467 |
| Opus 5 | $0.00020 | $0.00234 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
skill-maintainer 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 2d 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
Skill Maintainer
This skill maintains the repository's skill system.
Scope
Use it when:
- adding a new
skills/<name>/directory - changing how skills are discovered, invoked, or validated
- restoring skills after backup loss
- moving behavior between project docs and skill-specific docs
- preparing a public template that should keep only generic skills
Skill Structure
Every skill must have:
SKILL.md- YAML-style frontmatter with
nameanddescription - a concise scope section explaining when to use the skill
Optional files:
scripts/for deterministic commands the agent should run instead of retyping large logicreferences/for supporting docs that are too detailed for the main skill filetests/when scripts or parsing logic have behavior worth locking down
Maintenance Rules
- Keep skill-specific instructions in that skill's
SKILL.md. - Keep project-wide conventions in
AGENTS.mdordocs/. - Do not copy private project instructions into generic skills.
- If a change affects task lifecycle, task artifacts, skill discovery, skill execution, agent orchestration, restore behavior, or resume behavior, update project docs in the same source change.
- If a skill writes durable data, document whether that data belongs in
tasks/,data/, or runtime state such as.state/.
Verification
After changing skills, run:
.venv/bin/python skills/repo-health/scripts/check_repo_health.py
Run skill-specific tests when present, for example:
PYTHONPATH=skills/task-runner/scripts .venv/bin/python -m pytest skills/task-runner/tests
Publishing A Generic Template
When preparing a reusable public copy:
- keep core skills that implement task lifecycle and delegation
- remove or clearly separate personal integrations
- do not publish local
tasks/,data/,.state/, logs, credentials, or private runtime config - include sanitized examples only when they teach the generic workflow
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.
- 2d ago First seen · 64 lines · 40 tokens per session scan A 7cf5018a97fa
skill-maintainer is a skill published in the GitHub repository rdudov/task-agent (4 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 467 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.