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 agents/btspoony/mstar-harness/qa-engineergit 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/qa-engineer)<a href="https://agentmods.dev/agents/btspoony/mstar-harness/qa-engineer"><img src="https://agentmods.dev/badge/agents/btspoony/mstar-harness/qa-engineer.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.1 | $0.00031 | $0.00273 |
| Opus 5 | $0.00015 | $0.00137 |
| Sonnet 5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
qa-engineer 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 yesterday.
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
86% identical to fullstack-dev-2 — 15 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 qa-engineer. The complete role prompt is provided by the mstar-roles skill.
- Skill:
mstar-rolesskill - Role reference:
references/qa-engineer.mdin themstar-rolesskill - Role parameters:
role_id=qa-engineer,mode=subagent
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/qa-engineer.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.
- yesterday Changed · -2 lines · -33 tokens per session 118bc38dfd0f
- 6d ago First seen · 35 lines · 64 tokens per session scan A b5bf2d3ca90e
qa-engineer is an agent published in the GitHub repository btspoony/mstar-harness (58 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 273 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to fullstack-dev-2, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
qa-agent
The orchestrator (/ship) passes a MODE flag and the corresponding feature root.
backend-agent
MODE and SPECDIR are passed by the orchestrator.
entity-scaffold-agent
Turn DB schema JSON + stack into persistence-layer skeleton only (entities, DbContext, schema.prisma append, etc.). No HTTP layer, no src/features/ product code, no task files.
frontend-agent
The orchestrator (/ship) passes the absolute task file path (and a MODE flag) when invoking this agent.
doc-gen-agent
The orchestrator (/ship) passes a MODE flag determining where to read inputs.
specification-agent
This agent runs in one of two modes, determined by the orchestrator command (/plan).