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 btspoony/mstar-harness --skill pmgit clone --depth 1 https://github.com/btspoony/mstar-harnessWrote 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/btspoony/mstar-harness/pm)<a href="https://agentmods.dev/skills/btspoony/mstar-harness/pm"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/pm/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/btspoony/mstar-harness/pm"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00757 |
| Opus 5.5 | $0.00018 | $0.00303 |
| Sonnet 5.5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
pm 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 8d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM (entry shim)
Thin launcher only. Boot lists, iteration phases, Assignment templates, and SDD loops are not maintained in this file.
Workflow
Entry spelling differs per host; the active mstar-host reference owns it (command form, skill invocation form, session auto-load behaviour, iteration command names). This table keeps the routing only.
| Entry surface | Use |
|---|---|
Host ships a /pm command or exposes this pm skill |
→ project-manager for the session (general PM orchestration: single-plan, hotfix, QC waves, dispatch) |
| Host with no command entry | Same route: project-manager via mstar-roles → references/project-manager.md |
Formal iteration (host commands/ where shipped) |
Phase 1–5 sequencing by the host commands — without an iteration the shim still serves ordinary per-plan PM |
Iteration lifecycle (optional): host commands/ may sequence Phase 1–5; semantics SSOT → mstar-iteration. Not required for ordinary PM work.
Codebase audit (optional): /codebase-audit command → mstar-audit — read-only codebase survey producing prioritized, self-contained improvement plans. Output feeds iteration-start §1 Research or normal Prepare → Execute. Dispatched by PM under Task category: audit.
Detect host → mstar-host → the reference that detection resolves to (per-host entry, tool shapes and plan-mode bridges live only there).
Load Order
mstar-harness-coremstar-roles→references/project-manager.md— required reading list, routing, dispatch-first, iteration branch policy- Topic skills on demand per that file and the active workflow (
mstar-dispatch-gates,mstar-iteration,mstar-sdd,mstar-review-qc, …)
Decision Rules
- Delegate — PM does not implement, QC, or QA in-thread (
project-manager.mdExecution Boundary; hotfix →mstar-phase-gates). - Dispatch — when host has invoke/Task tools: 1 Assignment ⇒ 1 invoke (
mstar-dispatch-gates). Markdown alone is not dispatch. - SSOT — iteration lifecycle →
mstar-iteration; host Plan mode → the active host reference's plan-mode bridge (nested undermstar-host). - Autonomous Execute push — multi-plan iteration Phase 2–5: continuously dispatch implement → QC → QA → Done through merge-ready exit without routine yes/no prompts; Blocked only on true conflicts or metadata gaps →
mstar-iteration§2.6.
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.
- 8d ago Changed · -49 tokens per session 059acdcaa5b8
- 22d ago Changed · +6 lines 3b2bc2f508ed
- 1mo ago Changed · -1 lines · -5 tokens per session 9251de039c7c
- 1mo ago Changed · +2 lines 52d2ad495747
- 2mo ago First seen · 41 lines · 98 tokens per session scan A cce6bf2307a3
pm is a skill published in the GitHub repository btspoony/mstar-harness (66 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 757 once invoked, about $0.0002 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-30.
Other skills, from other repositories
comet-classic
A Chinese-language workflow guide for starting or resuming a structured software change using OpenSpec and Superpowers.
comet-native
A workflow for managing Native changes in Comet, where requirements, progress, and acceptance results are saved in project files. It uses the Comet command-line runtime to move through defined work stages.
comet-build
A Comet workflow step for turning an approved design into an implementation plan and completed code changes. Comet is the project workflow system described by the add-on.
grill-test
An end-to-end test workflow that runs a sequence of planning and implementation skills through real user confirmations and tests. It covers grilling an idea, writing a specification, creating tickets, implementing them, and reviewing the result.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.