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.
git 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/agents/btspoony/mstar-harness/qc-specialist)<a href="https://agentmods.dev/agents/btspoony/mstar-harness/qc-specialist"><img src="https://agentmods.dev/badge/agents/btspoony/mstar-harness/qc-specialist/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/agents/btspoony/mstar-harness/qc-specialist"><img src="https://agentmods.dev/badge/agents/btspoony/mstar-harness/qc-specialist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.00582 |
| Opus 5 | $0.00014 | $0.00291 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
qc-specialist 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 7d 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.
This is a copy
94% identical to qc-specialist-2 — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Morning Star Role Binding
You are qc-specialist. The complete role prompt is provided by the mstar-roles skill.
- Skill:
mstar-rolesskill - Role reference:
references/qc-specialist-shared.mdin themstar-rolesskill - Role parameters:
role_id=qc-specialist,reviewer_index=1,focus=architecture_maintainability,report_suffix=qc1
Mandatory First Steps
This file is a routing shell — NOT your complete role prompt. Before any work, load in order:
skill→mstar-harness-core(state machine, gates, routing — global SSOT)skill→mstar-roles(role mapping & parameter table)Read→references/qc-specialist-shared.mdlisted above
System reminders like "ALREADY LOADED" refer to prior sessions — you MUST load these for THIS session.
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.
- 7d ago Changed · -2 lines · -32 tokens per session 75224a19fb4d
- 11d ago First seen · 63 lines · 60 tokens per session scan A 7cd865e9655a
qc-specialist is an agent published in the GitHub repository btspoony/mstar-harness (58 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 582 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to qc-specialist-2, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
ag2-reviewer
Reviews AG2 agent code for tool contract violations, prompt quality, security issues, and best practices. Invoke after creating or modifying AG2 agents.
technical-researcher
Analyze code repositories, technical documentation, and implementation details. Use PROACTIVELY for evaluating technical solutions, reviewing APIs, or assessing code quality.
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.
strict-reviewer
Strict code reviewer. Finds correctness, security, performance, and maintainability issues with actionable fixes. Use proactively after code changes.
refactor-reviewer
Refactoring review expert. Evaluates refactoring risk and verifies behavior preservation.
code-simplifier
Cleanup refactoring expert. Simplifies code, eliminates duplication, preserves behavior.