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 commands/bumgeunsong/skill-up/upgrade-skillgit clone --depth 1 https://github.com/BumgeunSong/skill-upWrote 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/commands/bumgeunsong/skill-up/upgrade-skill)<a href="https://agentmods.dev/commands/bumgeunsong/skill-up/upgrade-skill"><img src="https://agentmods.dev/badge/commands/bumgeunsong/skill-up/upgrade-skill.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.00028 | $0.01247 |
| Opus 5 | $0.00014 | $0.00624 |
| Sonnet 5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
upgrade-skill 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Skill
Systematically improve a skill through test-driven evaluation and enhancement.
REQUIRED BACKGROUND: First invoke skill-up:writing-skills skill for TDD methodology applied to skills. See testing-skills-with-subagents.md in that skill's directory for pressure scenario templates.
Quick Reference
| Step | Action |
|---|---|
| 1 | Find and read the target skill |
| 2 | Create pressure scenario tests (RED) |
| 3 | Run baseline test without skill context |
| 4 | Evaluate discoverability (CSO check) |
| 5 | Identify gaps and improvements |
| 6 | Apply improvements (GREEN) |
| 7 | Re-test to verify (REFACTOR) |
| 8 | Update upgraded: true in stats |
Workflow
1. Locate Skill
Skill locations (check in order):
~/.claude/skills/{skill-name}/SKILL.md
~/.claude/plugins/**/skills/{skill-name}/SKILL.md
.claude/skills/{skill-name}/SKILL.md
If skill not found, report and exit.
2. Create Pressure Scenario Test
Generate 2-3 realistic scenarios that would trigger this skill:
Good scenario template:
SCENARIO: [Realistic situation where skill should apply]
Context:
- [Specific constraint 1]
- [Specific constraint 2]
- [Time/resource pressure]
Task: [What agent must do]
Success criteria:
- [ ] Agent recognizes skill applies
- [ ] Agent follows skill correctly
- [ ] Agent produces expected outcome
Pressure types to combine (pick 3+):
- Time pressure
- Sunk cost
- Authority override
- Exhaustion
- Pragmatic shortcuts
3. Run Baseline Test (RED Phase)
Spawn a subagent WITHOUT skill context:
- Give scenario only
- Document what agent does naturally
- Capture rationalizations verbatim
4. Evaluate Discoverability (CSO Check)
Check skill's search optimization:
| Check | Pass/Fail |
|---|---|
| Description starts with "Use when..." | |
| Description has specific triggers | |
| Keywords match search terms | |
| Name is verb-first, descriptive | |
| No workflow summary in description |
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 · 191 lines · 28 tokens per session scan A 5d4a0d5a66c5
upgrade-skill is a command published in the GitHub repository BumgeunSong/skill-up (11 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,247 once invoked, about $0.0001 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 commands, from other repositories
tdd-refactor
TDDのRefactorフェーズを実行します。テストを通す実装が完了した後、コード品質の改善とリファクタリングを行います。.
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
spec-impl
Execute spec tasks using TDD methodology.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
task-discard
PitWay: Abandon a dispatched task's worktree without integrating.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.