Skill Compose is an open-source platform for building and running AI agents that use modular skills. It is intended for creating skill-powered agents without workflow graphs or a command-line interface, and the catalogue skills are examples of those agent capabilities.
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/dp-archive/archive/skill-updaternpx skills add dp-archive/archive --skill skill-updatergit clone --depth 1 https://github.com/dp-archive/archiveWrote 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/dp-archive/archive/skill-updater)<a href="https://agentmods.dev/skills/dp-archive/archive/skill-updater"><img src="https://agentmods.dev/badge/skills/dp-archive/archive/skill-updater.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.1 | $0.00064 | $0.00958 |
| Opus 5 | $0.00032 | $0.00479 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
skill-updater 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 7d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Updater
This skill provides guidance for updating existing skills based on user feedback.
When to Use
Use this skill when:
- User provides feedback about an existing skill's performance
- User wants to improve or modify a skill
- User reports issues or bugs with a skill
- User wants to add new functionality to an existing skill
Required Inputs
- Skill Path: Path to the skill directory or .skill file to update
- Feedback: Description of what needs to change, improve, or be fixed
Update Process
Step 1: Load and Understand the Skill
Use the analyze_skill.py script to get a quick overview:
scripts/analyze_skill.py <skill-path>
This shows:
- Skill name and description
- SKILL.md line/word count
- All bundled resources (scripts/, references/, assets/)
- Any structural issues
Then read SKILL.md to understand the detailed instructions:
cat <skill-path>/SKILL.md
For .skill files (zip archives), extract first:
unzip <skill-path>.skill -d /tmp/skill-extract/
Step 2: Analyze the Feedback
Categorize the feedback into one or more types:
| Type | Example Feedback | Typical Changes |
|---|---|---|
| Bug fix | "The script fails when..." | Fix scripts, add error handling |
| Missing feature | "It should also support..." | Add new functionality |
| Clarity | "Instructions are confusing" | Improve SKILL.md documentation |
| Performance | "Too slow/uses too much context" | Optimize scripts, reduce SKILL.md |
| Trigger | "Doesn't activate when I say..." | Update description in frontmatter |
Step 3: Plan the Changes
Before making changes, create a clear plan:
- List specific files to modify
- Describe what changes each file needs
- Identify any new files to create or files to delete
- Consider impact on other parts of the skill
Step 4: Implement Changes
Apply changes following skill design principles:
For SKILL.md changes:
- Keep body under 500 lines
- Use imperative form
- Move detailed content to references/ if approaching limit
- Ensure frontmatter description captures all trigger scenarios
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 147 lines · 64 tokens per session scan A 98b8cab5d05d
skill-updater is a skill published in the GitHub repository dp-archive/archive (1,106 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 958 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-30.
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…