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 s977043/river-review --skill skill-creatorgit clone --depth 1 https://github.com/s977043/river-reviewWrote 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/s977043/river-review/skill-creator)<a href="https://agentmods.dev/skills/s977043/river-review/skill-creator"><img src="https://agentmods.dev/badge/skills/s977043/river-review/skill-creator.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.00103 | $0.01314 |
| Opus 5 | $0.00051 | $0.00657 |
| Sonnet 5 | $0.00021 | $0.00263 |
| Haiku 4.5 | $0.00010 | $0.00131 |
Grade A, and why
skill-creator 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- skill-creator — 89% identical, 142 lines differ
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern declaration
Primary pattern: Pipeline Secondary patterns: Inversion Why: skill creation requires strict phase order (requirements → pattern selection → structure → review) with an upfront question-gathering gate.
Purpose
Create a new skill only after the use case is concrete enough.
Your job is to:
- identify the smallest useful responsibility
- select the right design pattern
- define when the skill should trigger
- choose safe frontmatter defaults
- draft a minimal but strong
SKILL.md - propose supporting files only when they add clear value
- define an initial eval set
Safety constraints
Write output files only to .claude/skills/ unless the user explicitly specifies a different path.
Do not modify existing skills without user confirmation.
Note: this skill does not set disable-model-invocation: true because file creation is its primary purpose, not an incidental side effect. The settings.json deny list and user confirmation prompts provide sufficient guardrails.
Core rule
Do not create a broad or fuzzy skill.
Prefer:
- one responsibility
- one primary workflow
- one clear success condition
If the requested scope is too broad, split it into multiple skills.
Phase 0: Gate
Before drafting, confirm:
- target outcome
- primary user intent
- trigger phrases
- audience
- allowed tools needed
- whether the skill should be auto-invoked or manual-only
- source material available
- definition of done
If any item is unclear:
- ask the minimum focused questions, or
- inspect available files first if the answer can be found without asking
Do not draft the full skill until the gate passes.
Phase 0.5: Pattern selection
Choose the primary design pattern before drafting the skill.
Available patterns:
- Tool Wrapper — the skill mainly injects domain, library, or framework knowledge on demand
- Generator — the skill mainly produces structured output from a reusable template
- Reviewer — the skill mainly evaluates output against a checklist or rubric
- Inversion — the skill must gather missing information before acting
- Pipeline — the skill must enforce a strict multi-step workflow with checkpoints
What ships with it
4 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.
- 8d ago First seen · 214 lines · 103 tokens per session scan A 3827636e27fa
skill-creator is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 103 tokens to every session and 1,314 once invoked, about $0.0005 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-31.
Other skills, from other repositories
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…
logic-diff
Compare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side. Trigger when the user shares a refactor, rewrite, migration, or A/B implementation and wants to confirm behavior is unchanged — "did I break anything", "is this equivalent", "are these equivalent", "semantically…
omnicheck-gitlab
Use when checking if MR review findings have been applied — verifies both OmniForge-generated and human reviewer comments against the current diff, posts nudge replies on unaddressed threads.
omnicheck-github
Use when checking if PR review findings have been applied — verifies both OmniForge-generated and human reviewer comments against the current diff, posts nudge replies on unaddressed threads.
omnicreate-gitlab
Use when creating a GitLab merge request (OmniForge). Auto-populates title and description from commits, supports draft MRs, labels, assignees, reviewers, and issue linking.