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 skills add fortunto2/solo-factory --skill skill-auditgit clone --depth 1 https://github.com/fortunto2/solo-factoryWrote 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/fortunto2/solo-factory/skill-audit)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/skill-audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/skill-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fortunto2/solo-factory/skill-audit"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/skill-audit.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.01458 |
| Opus 5 | $0.00028 | $0.00729 |
| Sonnet 5 | $0.00011 | $0.00292 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
solo-skill-audit 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 10d 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.
This is a copy
91% identical to solo-skill-audit — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-audit
Audit a skill against the quality checklist based on Anthropic's internal best practices for Claude Code skills. Reads the skill's SKILL.md, references/, scripts/, and evaluates across 12 dimensions.
Source: https://x.com/trq212/status/2033949937936085378
Checklist Reference
- Scoring rubric, 12 dimensions:
references/checklist.md - The levers the scores measure — invocation, information hierarchy, leading words, failure modes:
references/writing-skills.md - Term definitions used in findings:
references/skills-glossary.md
Steps
-
Locate skill from
$ARGUMENTS:- If name: search
skills/{name}/SKILL.mdin current project, then~/.claude/plugins/**/skills/{name}/SKILL.md - If path: read directly
- If empty: list available skills via Glob
**/skills/*/SKILL.md, ask via AskUserQuestion
- If name: search
-
Read skill contents (parallel):
SKILL.md— main skill filereferences/*— all reference files (if dir exists)scripts/*— all scripts (if dir exists)assets/*— all assets (if dir exists)- Count total lines of SKILL.md
-
Read checklist from
references/checklist.md -
Evaluate each dimension — for every checklist item, assess based on what you read:
For each of the 12 dimensions:
- State what you found (evidence)
- Score 0, 1, or 2 (use rubric from checklist)
- If score < 2: give one specific fix
-
Determine category — classify skill into one of 9 types from checklist. Flag if it straddles multiple.
-
Failure-mode pass — read
references/writing-skills.md, then check the skill for each named failure mode. Quote the offending line for every hit; a hit with no quote is a guess:- No-op — a line the model already obeys by default. Test each sentence in isolation: does it change behaviour versus the default?
- Duplication — one meaning stated in more than one place.
- Sediment — stale lines describing behaviour, paths, or tools that no longer exist.
- Sprawl — long even after no-ops and duplication are removed; cure is disclosure into
references/, not deletion. - Negation — steering by prohibition where a positive target would work.
Don't use Xnames X;use Ydoesn't. - Premature completion — a step whose completion criterion can't distinguish done from not-done.
- Weak leading word — a description or body leaning on generic words instead of a compact pretrained concept the user actually types.
What ships with it
3 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.
- 10d ago First seen · 116 lines · 57 tokens per session scan A 0e0eee7e8e85
solo-skill-audit is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,458 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to solo-skill-audit, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
harness
Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
dev-plan
Generate a development plan with task breakdown and section 10 tracking tables.
product-diagnosis
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.
harness-review
Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.