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-strategygit 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-strategy)<a href="https://agentmods.dev/skills/btspoony/mstar-harness/mstar-strategy"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-strategy/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-strategy"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-strategy.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.00076 | $0.01302 |
| Opus 5 | $0.00038 | $0.00651 |
| Sonnet 5 | $0.00015 | $0.00260 |
| Haiku 4.5 | $0.00008 | $0.00130 |
Grade A, and why
mstar-strategy 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mstar-strategy（全局战略方向）
Load order
Read mstar-harness-core first. Path symbols → mstar-conventions. On conflict, mstar-harness-core wins.
Purpose
STRATEGY.md is the project's upstream anchor — a concise declaration of what the project is, where it's going, and what principles guide decisions. It is read as grounding by brainstorm, plan, and ideation phases so strategic choices flow into every feature.
Without a strategy document, decisions are made in isolation — each plan misses the larger context.
产物存储位置
SSOT: mstar-conventions/references/artifact-storage-paths.md。STRATEGY.md → <repo-root>/STRATEGY.md（与 .git/、AGENTS.md 同级）。禁止放入 {HARNESS_DIR}、docs/ 或任何子目录。
When to use
| Trigger | Example |
|---|---|
| Project initialization | "Create STRATEGY.md for this new project" |
| Directional change | "We're pivoting from monolith to microservices" |
| PM requests alignment | "Check if this plan aligns with our strategy" |
| Periodic review | "Review and update STRATEGY.md" |
STRATEGY.md structure
A good strategy document is opinionated and concise. It should fit in one screen of reading.
Required sections
# Strategy
## Vision
<1-2 sentences: what the project aims to become>
## What we build
<Core product/users/use cases>
## What we don't build
<Explicit non-goals — as important as goals>
## Guiding Principles
- <Principle 1>
- <Principle 2>
- <Principle 3>
## Technology Direction
<Key tech choices and rationale>
## Decision Log
<Major past decisions with context — why, not just what>
Engine check (when available): run
mstar lint <STRATEGY.md>(orimport { lintStrategySections } from "@mstar-harness/engine"in a host hook) to check the six required sections above (Vision, What we build, What we don't build, Guiding Principles, Technology Direction, Decision Log). Onfail-> do not proceed; fix and re-run. Skill text below remains authoritative when the runtime is absent.
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.
- 11d ago First seen · 115 lines · 76 tokens per session scan A 5f35070b7e71
mstar-strategy is a skill published in the GitHub repository btspoony/mstar-harness (58 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,302 once invoked, about $0.0004 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-open
A guide for starting an OpenSpec change: a tracked software task with proposal, design, task, and state files. It also covers choosing or restoring the correct project workspace and output language.
comet-build
Comet Phase 3: Plan and Build. Invoke with /comet-build. Create plans and select execution method (subagent or direct) for implementation.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.