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-checkgit 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-check)<a href="https://agentmods.dev/commands/stevesolun/micro-skills/skill-check"><img src="https://agentmods.dev/badge/commands/stevesolun/micro-skills/skill-check.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.00026 | $0.00490 |
| Opus 5 | $0.00013 | $0.00245 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
skill-check 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 5d 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
Run the Check gate from the micro-skill pipeline against the current work.
If $ARGUMENTS specifies a skill name, use it to load skill-level gates. If not specified and the active skill cannot be inferred from context, ask: "Which converted skill is active? Run /skill-list to see options."
Steps
-
Load universal gate questions (always applied):
- Does the output match what was requested?
- Are all stated constraints satisfied?
- Does every element serve a purpose (no dead code, no placeholder text)?
- Is the output usable as-is with no manual fixes?
- If code: does it run without errors?
- If file: is the format correct and complete?
- If multi-component: do components integrate correctly?
-
Load project-level gates: Look for
check-gates.mdin the project root or.claude/directory. If found, add all questions to the gate list. -
Load skill-level gates: If a specific converted skill is active (identified by context or user specification), look for
check-gates.mdin${CLAUDE_PLUGIN_DATA}/converted/<skill-name>/. If found, add all questions. -
Load failure logs: Merge patterns from:
- Project-level
failure-log.md(project root) - Skill-level
failure-log.md(${CLAUDE_PLUGIN_DATA}/converted/<skill-name>/) Each pattern becomes an additional constraint to check against.
- Project-level
-
Answer every question YES or NO. Be honest. "Mostly yes" = NO.
-
Report results:
- List each question with its YES/NO answer and source (universal/project/skill)
- For each NO: state what is wrong in one sentence
- Offer to fix each failure
-
After fixing and re-passing all gates:
- Ask whether to append new failure patterns to
failure-log.md - If yes, append to both project-level and skill-level logs
- Ask whether to append new failure patterns to
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.
- 5d ago First seen · 41 lines · 26 tokens per session scan A 333f71e8be8f
skill-check is a command published in the GitHub repository stevesolun/micro-skills (11 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 490 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.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.