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 mstar-project-governancegit 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/mstar-project-governance)<a href="https://agentmods.dev/skills/btspoony/mstar-harness/mstar-project-governance"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-project-governance/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/mstar-project-governance"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-project-governance.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.00159 | $0.02391 |
| Opus 5 | $0.00079 | $0.01196 |
| Sonnet 5 | $0.00032 | $0.00478 |
| Haiku 4.5 | $0.00016 | $0.00239 |
Grade A, and why
mstar-project-governance 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 12d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mstar-project-governance（项目治理层：roadmap + register）
Load Order
- 先 Read
mstar-harness-core（SKILL.md；冲突时以 core 为准）。 - 路径符号（
{PROJECT_DIR}/{WORKFLOW_DIR}解析与.mstarc声明）→mstar-conventions。 - 字段语义 SSOT（severity 含义、findings cleanup modes、close 协议全文、engine-check 查询）→
mstar-artifacts（references/status-and-residuals.md）。本 skill 只承载编写约定与生命周期规则，不重复字段全文。
Scope
项目层 = {PROJECT_DIR}/<id>/（默认 {HARNESS_DIR}/projects/<id>/；.mstarc project_dir 声明时用声明值）：
| 文件 | 内容 |
|---|---|
roadmap.md |
项目方向与目标（frontmatter machine-checkable + body 约定） |
residuals.json |
项目 register：open residual 的 SSOT（entries[<plan-id>] 数组） |
references/ |
主题化研究语料（surveys / epic 备注 / 第三方 notes）。与 {SPECS_DIR}（冻结规格/ADR）、{KNOWLEDGE_DIR}（compound 结晶实现 SSOT）、{ITERATION_DIR}（迭代 package）不同；engine 只列文件名（listProjectReferenceFiles），不做 markdown schema 校验 |
_default回退：无项目流程（未指定 project id 的 plan / 单 plan / hotfix）落到projects/_default/（engine_DEFAULT_PROJECT）。项目归属由 plan 的 project id 决定；未归属即_default。- 本 skill 的 schema 事实与
packages/engine/src/project.ts逐字一致（validateRoadmap/validateProjectRegister/findingsCleanupGate/techDebtRollup）；技能文本是语义 SSOT，engine 是确定性校验。
Roadmap 编写约定（projects/<id>/roadmap.md）
Frontmatter schema（machine-checkable；engine validateRoadmap）
---
project_id: <id>
title: <title>
status: active | paused | completed
created_at: YYYY-MM-DD
milestones: [ ... ] # optional
residuals_ref: residuals.json # optional
---
# <title>
## Direction
...
| 字段 | 必填 | 规则 |
|---|---|---|
project_id |
是 | 非空字符串 |
title |
是 | 非空字符串 |
status |
是 | 枚举 `active |
created_at |
是 | YYYY-MM-DD |
milestones |
否 | 非空字符串列表（空 milestones: 视同缺省） |
residuals_ref |
否 | 非空字符串（指向 register 文件，如 residuals.json） |
Body 约定（warnings only —— 永不翻转 ok）
- 应有
## Direction小节陈述项目方向。 - 目标项以 markdown task-list 列出：
- [ ]计划/进行中，- [x]已交付。 - 无 residual→goal 自动链接（本迭代 Non-Goal）：goal items 不携带 register id；residual 与目标的对齐是人工约定，不是硬门禁。
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.
- 12d ago First seen · 120 lines · 159 tokens per session scan A cd23cfbcc78a
mstar-project-governance is a skill published in the GitHub repository btspoony/mstar-harness (57 stars, last pushed today), licensed MIT. It adds 159 tokens to every session and 2,391 once invoked, about $0.0008 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-30.
Other skills, from other repositories
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.
comet-classic
A Chinese-language workflow guide for starting or resuming a structured software change using OpenSpec and Superpowers.
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-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
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.