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/romerma/mstack/commitnpx skills add romerma/mstack --skill commitgit clone --depth 1 https://github.com/romerma/mstackWhat 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.00063 | $0.00972 |
| Opus 5 | $0.00032 | $0.00486 |
| Sonnet 5 | $0.00013 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
The log is read by people who were not in the session. A subject that made sense with the diff
open in front of you is not the test. The test is whether it still says something six months
later in git log --oneline.
$ARGUMENTS
The shape
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
The colon and the space after it are required. So is the description.
Pick the type
Two are fixed by the spec and the rest are convention:
featwhen the commit adds a feature. This is the only thing that earnsfeat.fixwhen the commit repairs a bug. Not "touched a file under src/".docs,test,refactor,perf,build,ci,style,chore,revertfor everything else.
The type is a claim about the change, and a wrong one is a lie the release tooling believes:
fix cuts a PATCH release, feat cuts a MINOR one, and a breaking change cuts a MAJOR one.
Reaching for chore because the change is hard to classify is how a feature ships unreleased.
A scope is optional. Use one when the repository has real sections a reader would recognise
(fix(parser):), and leave it off rather than inventing one.
Write the description
The spec says only that a description follows the colon and space. These are this repository's rules on top of it, and calling them "the standard" would be wrong:
- Imperative mood. "add the receipt", not "adds", "added" or "the receipt". Read it as
this commit will
<description>. - Lower case after the colon, and no full stop at the end.
- 72 characters or fewer for the whole subject line, type included.
- Name the change, not the file. "fix the gate" says nothing that
--statdoes not. - One commit, one change. If the description needs an "and" joining two unrelated things, it is two commits.
Breaking changes
Mark them in the prefix with !, in a footer, or both:
feat(api)!: take the store root from the manifest
BREAKING CHANGE: MSTACK_ROOT is no longer read.
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.
- yesterday First seen · 93 lines · 63 tokens per session scan A 5c6cecf2bfbe
commit is a skill published in the GitHub repository romerma/mstack (1 stars, last pushed 8d ago), licensed MIT. It adds 63 tokens to every session and 972 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-31.
Other skills, from other repositories
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…
forensics
Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…