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 agentmods add commands/btspoony/mstar-harness/codebase-auditgit 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/commands/btspoony/mstar-harness/codebase-audit)<a href="https://agentmods.dev/commands/btspoony/mstar-harness/codebase-audit"><img src="https://agentmods.dev/badge/commands/btspoony/mstar-harness/codebase-audit.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00047 | $0.00755 |
| Opus 5 | $0.00023 | $0.00378 |
| Sonnet 5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
codebase-audit 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 4d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Codebase
Run a read-only codebase audit that discovers what is worth doing and writes self-contained plans for the normal Prepare → Execute flow.
Read-only. No source edits, no state machine, no commits. Output: prioritized plans in {PLAN_DIR}/audit-<date>/.
Boot
mstar-harness-coremstar-audit→ SKILL.md（common core：hard rules、recon、vet、variant dispatch、## Plan output (all variants)）+references/codebase-audit.md（full-audit 变体：Phase 2 类别 + effort、scope variants、Phase 4 变体细则、audit index 模板）mstar-roles→references/code-reviewer.md（执行角色：audit 执行体）mstar-conventions(path symbols —{PLAN_DIR},{HARNESS_DIR})mstar-host→ active host reference (invoke capability for parallel subagents)
Routing（谁执行 audit）
| Context | Who runs the audit |
|---|---|
| Small repo (single scan pass feasible) | PM dispatches @code-reviewer — single scan pass, then vet and write plans |
| Large repo (parallel categories needed) | @code-reviewer fans out read-only scout / explore subagents per category via Assignment Delegation: allowed (scout/explore only, read-only), then vets and writes plans |
| Specialist depth needed | PM orchestrates an @architect consult for architecture/tech-debt depth (separate dispatch, or folded into the audit delegation brief) |
This command is the PM entry point; the audit execution body is code-reviewer（PM dispatch）.
The audit is advisory — it does not enter the per-plan state machine (Todo → InProgress → InReview → Done). Its output is plan candidates.
Execute
Execute mstar-audit end to end（SKILL.md common core：Recon → Vet & prioritize；full-audit detail：references/codebase-audit.md —— Phase 2 九类别 fan-out、effort quick / standard / deep、scope variants bare / quick / deep / category focus（security / perf / tests, ...）/ branch / next / roadmap / simplify、Phase 4 变体细则、audit index 输出模板；plan writing → SKILL.md ## Plan output (all variants)）。Plans → {PLAN_DIR}/audit-<YYYY-MM-DD>/NNN-<slug>.md + README.md index，per mstar-artifacts/references/plan-quality-bar.md。
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.
- 4d ago First seen · 41 lines · 47 tokens per session scan A 8e8a5c9735f1
codebase-audit is a command published in the GitHub repository btspoony/mstar-harness (57 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 755 once invoked, about $0.0002 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 commands, from other repositories
status
Pipeline status for a spec/feature — or, with no slug, the whole-project delivery report (every spec/backlog/quick-task + GitHub/Linear cross-ref).
dashboard
Launch the local planr dashboard — a live, read-only view of the .planr/ graph (Overview · Graph · Board · List · Sprints · Activity). Reuses a running server if one already owns the port.
sync
Reconcile spec ↔ quick-task ↔ issue-tracker alignment across .planr/ — guarantee every shippable spec carries its externalization Quick Task (the unit pushed to Linear/GitHub for PO + manager visibility), fix deterministic drift, surface judgment calls. Read-only by default.
csm-goals
List, set, or update tracked goals for this project.
init
Initialise the planning seed and record the human team, roles, and escalation channels.
statuswt
You are checking the status of all active worktree task files in the project.