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 skills/stephenqiu30/stephen-claude/commitnpx skills add StephenQiu30/stephen-claude --skill commitgit clone --depth 1 https://github.com/StephenQiu30/stephen-claudeWhat 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 | $0.00036 | $0.00599 |
| Opus 5 | $0.00018 | $0.00300 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 36 tokens to every session and 599 once invoked, about $0.0002 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
fireworks-tech-graph
Create technical diagrams such as software architecture, data flow, flowcharts, sequence diagrams, C4 reviews, cloud deployments, event streams, observability investigations, agent/memory systems, UML, ER, network topology, timelines, and technical concept maps, then export SVG, PNG, focused semantic SVG-to-GIF…
loop-verifier
Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
decision-heuristics
当用户在重大选择上纠结（换工作/买房/搬城/合伙/结婚）、列了利弊表还是拿不定主意时调用。 核心理念: 无法决定就答否; 三个重大决定(住哪/和谁/做什么)值得花一两年; 两个均等选择选短期更痛苦的路。 不适用于: 日常琐碎选择（晚饭吃什么）、信息查询。 Triggers: 纠结/拿不定主意/要不要/该不该/利弊/decision/hesitate/should I.
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
monkey-mind-meditation
当用户脑子停不下来、焦虑反刍、想学冥想/提升专注力时调用。 核心理念: 内心独白(心猴)是失控程序不是"我"; 用调试模式逐条观察念头, 意识到即失去控制; 冥想=收件箱归零/心灵间歇性禁食。 不适用于: 严重精神疾病急性发作(先就医); 需要立刻处理的实际问题(先做事)。 Triggers: 冥想/焦虑/脑子停不下来/胡思乱想/专注/心猴/monkey mind/meditation/anxiety.