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/implementnpx skills add romerma/mstack --skill implementgit 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.00060 | $0.00644 |
| Opus 5 | $0.00030 | $0.00322 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
implement 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement
Delegate this to mstack:implementer rather than doing it in the main session. The gain is
review separation: a pass that wrote the code cannot review it, and "it was faster to do it
myself" trades away the only structural check in the workflow.
Where the contract lives
On the spec path, work from .mstack/specs/<slug>/ and execute tasks.md in order, ticking
each box as you finish. Not from the issue, and not from the acceptance array: the spec is
what was reviewed.
On the direct path, the item's acceptance array is the contract. Do not widen it. If the work
turns out to need something outside it, that is a finding, not a licence.
While you work
Keep .mstack/progress/current.md updated as you go, not at the end. Its last section
answers one question: if this session stops right now, what should the next one do first.
mstack decide --phase implement --decision "..." --why "..." --evidence "..." --result "..."
One row is one decision. If it does not fit on one line, the decision is not crisp yet.
Tests
Every behaviour change gets a test that fails without the change. Check that: revert the change locally and watch it go red. A test that passes either way is not coverage, it is decoration.
Never weaken an existing test to get green. If a test is genuinely wrong, fix it deliberately, in its own commit, with the reason recorded. That is a different act from making a failure go away, and the commit history should show which one happened.
Prefer no new test over a bad one. A bad test is one that mostly exercises mocks, encodes current implementation details, depends on timing or global state, or would be deleted the moment it had proved its point.
The report
.mstack/progress/impl_<slug>.md:
- What changed, in a paragraph.
- Files, the real list.
- Commands, fenced, with the actual output pasted. Not a summary of it.
- R to test: each requirement, the test that covers it, and the
file:linewhere that test lives. On the direct path, map acceptance bullets instead.
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 · 64 lines · 60 tokens per session scan A dc00c7014747
implement is a skill published in the GitHub repository romerma/mstack (1 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 644 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"…