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-design-mdgit 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-design-md)<a href="https://agentmods.dev/skills/btspoony/mstar-harness/mstar-design-md"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-design-md/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-design-md"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-design-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 71 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00060 | $0.02475 |
| Opus 5.5 | $0.00024 | $0.00990 |
| Sonnet 5.5 | $0.00012 | $0.00495 |
| Haiku 4.5 | $0.00006 | $0.00248 |
Grade A, and why
mstar-design-md 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 today.
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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load order
Before first Read of this skill: Read mstar-harness-core (SKILL.md). For Prepare phase integration and gate rules, read mstar-phase-gates. For plan directory paths ({HARNESS_DIR}, {SPECS_DIR}), read mstar-conventions. On conflict, mstar-harness-core wins.
| 你还可能要 Read | 何时 |
|---|---|
mstar-phase-gates |
Prepare 阶段判定 gate、何时 DESIGN.md 必须就绪 |
mstar-conventions |
{HARNESS_DIR} / {SPECS_DIR} 路径解析 |
mstar-roles |
@architect / @product-manager / @frontend-dev / @qc-specialist / @qa-engineer 角色职责边界 |
mstar-coding-behavior |
实现角色消费 DESIGN.md 前的通用编码约束 |
mstar-design-system |
一个实现需要收敛到既有 baseline（原型 / 设计导出 / 既有产品标记 / 书面契约）时：baseline 定位与机器化、三层 parity、defect/decision/phantom 分诊、coverage 证据 |
Scope (DESIGN.md lifecycle)
| Topic | See |
|---|---|
| Normative spec: section definitions, token naming, light/dark rules, YAML frontmatter structure | references/design-md-spec.md |
| Three-level completeness checklist (MVP / Standard / Production) | references/completeness-checklist.md |
| Vercel Geist DESIGN.md as annotated reference | references/vercel-example.md |
| Full template with YAML frontmatter and Level 2/3 placeholders | templates/DESIGN.md.template |
| Dark theme template (same token names, different values) | templates/DESIGN.dark.md.template |
YAML frontmatter is the SSOT for token values. Colors, typography, spacing, rounded, and components live in the frontmatter as structured, machine-readable data. The Markdown body is supplementary documentation (rules, intent, usage guidance). When reading DESIGN.md, always parse the YAML frontmatter first; when writing, keep frontmatter and body in sync.
Out of scope: rendered UI preview tooling outside the repo; frontend implementation that consumes DESIGN.md tokens (use @frontend-dev / @fullstack-dev); QC review verdict rules (→ mstar-review-qc).
Location
- Primary: project root
DESIGN.md(human + agent visible, aligns withAGENTS.md) - Dark theme: project root
DESIGN.dark.md(same token names, different values) DESIGN.mdis a project-level design contract, not a harness internal artifact. It lives besideREADME.mdandAGENTS.md.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +12 lines 51ae95e2f125
- 6d ago Changed · -161 tokens per session 6707a311655c
- 1mo ago First seen · 143 lines · 221 tokens per session scan A 19c0a5fae422
mstar-design-md is a skill published in the GitHub repository btspoony/mstar-harness (64 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 2,475 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
planr-design
Run OpenPlanr design, design-loop, or design-review using portable board assets.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
comet
Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.
comet-classic
A Chinese-language workflow guide for starting or resuming a structured software change using OpenSpec and Superpowers.
comet-design
Comet Phase 2: Deep Design. Invoke with /comet-design. Produce Design Doc and delta spec through brainstorming.