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 myclaude-sh/myclaude-creator-engine --skill sample-productgit clone --depth 1 https://github.com/myclaude-sh/myclaude-creator-engineWrote 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/myclaude-sh/myclaude-creator-engine/sample-product)<a href="https://agentmods.dev/skills/myclaude-sh/myclaude-creator-engine/sample-product"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/sample-product/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/myclaude-sh/myclaude-creator-engine/sample-product"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/sample-product.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.00061 | $0.01149 |
| Opus 5 | $0.00030 | $0.00575 |
| Sonnet 5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
commit-review 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Review
Systematic review of git commits for message quality, diff hygiene, and common mistakes before pushing.
Version: 1.0.0 Category: Skills Author: @sample-creator
When to Use
- You want to review your commits before pushing to a shared branch
- You need to check if commit messages follow conventional format
- You want to catch common mistakes (large files, secrets, debug code)
- A PR has commits that need cleanup before merge
When NOT to Use
- For full code review (use a dedicated code review tool instead)
- For CI/CD pipeline checks (this is a pre-push local review)
- For rebasing or rewriting history (this reviews, not rewrites)
Activation Protocol
Before responding to any invocation:
- Load review criteria: Read
${CLAUDE_SKILL_DIR}/references/review-criteria.md— Contains: commit message format rules, diff size thresholds, anti-patterns - Load examples: Read
${CLAUDE_SKILL_DIR}/examples/good-vs-bad.md— Contains: 5 examples of good commits vs. problematic commits - Identify scope: How many commits to review? Last N, a range, or all unpushed?
- Run question system: Check for required inputs (see below)
Question System
| Input | Required | If Missing |
|---|---|---|
| Commits to review | Yes | Ask: "How many recent commits should I review? Or give me a range (e.g., HEAD~3..HEAD)" |
| Branch context | No | Default: current branch. State assumption. |
| Strictness level | No | Default: standard. Options: relaxed (personal project), standard, strict (team/OSS) |
Core Instructions
Review Pipeline
For each commit in the review scope:
Step 1 — Message Quality
- Does the message follow conventional format? (
type: subjectortype(scope): subject) - Is the subject line under 72 characters?
- Does it explain WHY, not just WHAT?
- Is it written in imperative mood? ("add feature" not "added feature")
Step 2 — Diff Analysis
- How many files changed? Flag if >10 files (might need splitting)
- How many lines added/removed? Flag if >500 lines net
- Are there unrelated changes mixed in? (scope creep)
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 · 145 lines · 61 tokens per session scan A 558d0d8cf7cb
commit-review is a skill published in the GitHub repository myclaude-sh/myclaude-creator-engine (25 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 1,149 once invoked, about $0.0003 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 skills, from other repositories
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
developer-workflow
Use when the user is writing, reviewing, debugging, testing, or refactoring code, or wants help with commits and pull requests. Emphasizes reading existing code first, verifying changes, and never inventing APIs.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
chezmoi-sync
Interactive chezmoi drift check and sync. TRIGGERS - chezmoi sync, sync dotfiles, dotfile drift, chezmoi guard, chezmoi check.