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 StephenQiu30/stephen-claude --skill commitgit clone --depth 1 https://github.com/StephenQiu30/stephen-claudeWrote 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/stephenqiu30/stephen-claude/commit)<a href="https://agentmods.dev/skills/stephenqiu30/stephen-claude/commit"><img src="https://agentmods.dev/badge/skills/stephenqiu30/stephen-claude/commit/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/stephenqiu30/stephen-claude/commit"><img src="https://agentmods.dev/badge/skills/stephenqiu30/stephen-claude/commit.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.00036 | $0.00599 |
| Opus 5.5 | $0.00014 | $0.00240 |
| Sonnet 5.5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
commit 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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Goals
- Produce a commit that reflects the actual code changes and the session context.
- Follow
WORKFLOW.mdandCLAUDE.mdcommit discipline (allowed types and test-first ordering). - Include both summary and rationale in the body.
Allowed commit types
Only these subject prefixes are allowed:
test:— failing tests, fixtures, mocks, acceptance scripts, test-only expectationsimpl:— smallest implementation that makes existing red tests passfeat:— user-visible capability or behavior changes (after priortest:unless documented as not scriptable)refactor:— behavior-preserving cleanup after tests are greendocs:— documentation, examples, workflow text, acceptance noteschore:— CI, configuration, dependency metadata, generated housekeeping
For feature or behavior work, preserve order: test: first, then impl:/feat:, then optional refactor:, docs:, or chore:.
Do not mix unrelated types in one commit. Split by type when practical.
Inputs
- Session history for intent and rationale.
git status,git diff, andgit diff --stagedfor actual changes.WORKFLOW.md,CLAUDE.md, and workpadCommit Planwhen present.
Steps
- Read session history to identify scope, intent, and rationale.
- Inspect the working tree and staged changes (
git status,git diff,git diff --staged). - Stage intended changes (
git add -A) after confirming scope. - Sanity-check newly added files; flag build artifacts, logs, or temp files before committing.
- If staging is incomplete or includes unrelated files, fix the index or ask for confirmation.
- Choose the allowed type that matches the staged diff. Do not use
fix:or scoped conventional types unless documented as an exception. - Write a subject line in imperative mood, <= 72 characters. Format:
<type> <short summary>. - Write a body with summary, rationale, and tests or validation run (or why not run).
- Wrap body lines at 72 characters.
- Create the commit message with a here-doc or temp file and use
git commit -F <file>. - Commit only when the message matches the staged changes.
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.
- 1mo ago First seen · 70 lines · 36 tokens per session scan A 0d65628011f9
commit is a skill published in the GitHub repository StephenQiu30/stephen-claude (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 599 once invoked, about $0.0001 per session on Opus 5.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
ziw-pr
Use when opening, refreshing, or shipping the current branch as a pull request with Conventional Commits, push, PR creation, and issue linking, in bounded fix rounds; hooks and CI are the check gate.
roadmap-task-deliver
Deliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.
plan-deliver
Autonomously deliver an approved implementation plan to a ready GitHub pull request. Use when the user supplies a plan in the conversation or a file and authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback; use jira-issue-deliver when the…
phase-commit
Create one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.
know-code
Gate git commit, git push, and PR creation until the human passes a comprehension quiz about the current code changes. Use when commit/push/PR is blocked by know-code, when the user asks to run know-code or verify they understand the diff, or before shipping. Start with know-code range begin for multi-commit work. Run…
git-commit-guide
A guide for making Git commits, which are saved snapshots of code changes, in small logical units with consistent messages and pre-commit checks.