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-artifactsgit 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-artifacts)<a href="https://agentmods.dev/skills/btspoony/mstar-harness/mstar-artifacts"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-artifacts/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-artifacts"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-artifacts.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.00222 | $0.02041 |
| Opus 5 | $0.00111 | $0.01020 |
| Sonnet 5 | $0.00044 | $0.00408 |
| Haiku 4.5 | $0.00022 | $0.00204 |
Grade A, and why
mstar-artifacts 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 — 67 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), and mstar-conventions when path symbols matter. Git branch / worktree / QC checkout → mstar-branch-worktree. On conflict, mstar-harness-core wins.
Scope (plan directory artifacts)
| Topic | See |
|---|---|
| Main plan, review bundle naming, durable summaries, QC waves, residual and plan index order | references/plan-files-and-reports.md |
| Plan template (Global Constraints, Interfaces) | templates/plan.main.md |
| knowledge / iterations / specs boundaries and indexes | references/knowledge-and-designs.md |
status.json (v2 root), workflow snapshots, project register, residual severity / lifecycle, engine-check queries |
references/status-and-residuals.md |
Empty-repo status.json template |
templates/status.empty.json (templates/README.md) |
| Tech-debt rollup (read-only) | mstar status tech-debt [path] (engine techDebtRollup; see references/status-and-residuals.md) |
Out of scope: branch and QC/QA checkout alignment → mstar-branch-worktree; leaf QC checklist and verdict → mstar-roles/references/qc-specialist/; PM QC orchestration → mstar-review-qc; {HARNESS_DIR} discovery and init → mstar-conventions.
status.json, workflow snapshots, and open residual (summary)
{HARNESS_DIR}/status.json(v2): active-lifecycle register —{ version: 2, updated_at, workflows[] }. Each entry points at its snapshot dir (dir: workflows/<id>); terminal lifecycles are unregistered after the snapshot write.{WORKFLOW_DIR}/<id>/snapshot.json: per-lifecycle running state —plans[]rows (legacy PlanRow shape verbatim) + per-rowexecution_lease+ top-levelintegration_merge_lease/execution_policy/branchanchors /control_worktree_path.{PROJECT_DIR}/<id>/residuals.json: open residual register,entries[<plan-id>]arrays — the open-list SSOT (severity enum + lifecycle semantics verbatim; project-less flows use_default).- Canonical: register new findings only in the project register (
projects/<id>/residuals.json); v1 rootresidual_findingsis legacy read-only — migrate viamstar migrate, do not dual-write.
What ships with it
7 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.
- 11d ago First seen · 67 lines · 222 tokens per session scan A d9ddfa1803e8
mstar-artifacts is a skill published in the GitHub repository btspoony/mstar-harness (58 stars, last pushed yesterday), licensed MIT. It adds 222 tokens to every session and 2,041 once invoked, about $0.0011 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-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.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
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-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.