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/stevesolun/micro-skills/skill-failgit clone --depth 1 https://github.com/stevesolun/micro-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/commands/stevesolun/micro-skills/skill-fail)<a href="https://agentmods.dev/commands/stevesolun/micro-skills/skill-fail"><img src="https://agentmods.dev/badge/commands/stevesolun/micro-skills/skill-fail.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.00014 | $0.00249 |
| Opus 5 | $0.00007 | $0.00125 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
skill-fail 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.
What it actually says
Append a failure pattern to the failure logs.
Steps
-
Project-level log: Find
failure-log.mdin the project root. If it doesn't exist, create it with the header:# Failure Log One-line patterns learned from past mistakes. -
Skill-level log: If a skill name is specified via
--skill <name>or can be inferred from context, findfailure-log.mdin${CLAUDE_PLUGIN_DATA}/converted/<skill-name>/. If it doesn't exist, create it with the same header. If the skill name cannot be determined, skip the skill-level log and note that only the project-level log was updated. -
Compress the description to under 10 words if needed.
-
Append this line to both logs (use YYYY-MM-DD format for the date):
- [YYYY-MM-DD] check: $ARGUMENTS -
Confirm what was added and to which logs.
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 · 28 lines · 14 tokens per session scan A 67574626b251
skill-fail is a command published in the GitHub repository stevesolun/micro-skills (11 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 249 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
autoworker
Start the autoworker execution workflow for any non-trivial task.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.