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-e2egit 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-e2e)<a href="https://agentmods.dev/skills/btspoony/mstar-harness/mstar-e2e"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-e2e/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-e2e"><img src="https://agentmods.dev/badge/skills/btspoony/mstar-harness/mstar-e2e.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.00058 | $0.01057 |
| Opus 5.5 | $0.00023 | $0.00423 |
| Sonnet 5.5 | $0.00012 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
mstar-e2e 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 8d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Independent E2E Verification
Load Order
Read mstar-harness-core first. PM follows mstar-roles → references/project-manager.md and the existing dispatch/path contracts; the assigned executor reads mstar-roles → references/ops-engineer.md. Resolve available host tools through mstar-host only when needed. No external skill, CLI, or MCP is a required dependency.
Scope
This is an explicitly requested verification workflow, separate from development iterations and routine QA. Trigger phrases include “run these E2E scenarios”, “verify on this device”, “check the installed deployment”, and /amazing-e2e-check. A UI diff, missing screenshot, failed unit test, or reviewer suggestion does not authorize it.
External-dependency language in a development AC (live API, provider receipt, authenticated/named host or account, installed plugin/artifact, real browser/device, deployed environment) does not itself trigger this skill. Prepare rewrites that AC to isolated/local proof; only the user's separate explicit scenario authorization triggers real-environment verification.
Workflow
- PM scopes the request. Record the existing user authorization, build/ref, environment/device, named scenarios and expected results, permitted side effects, capability, and report path. Ask only for missing required inputs; never infer production, accounts, or devices. Reuse relevant knowledge without a new global scan.
- PM registers independent work. Use existing workflow
type: plan, its own workflow/plan IDs and working context. Workflow states (read through the public workflow view against current authority) arerunning | paused | completed | failed | stopped; plan rows useTodo → InProgress → InReview → Done/Blocked. Do not insert an iteration phase, ordinary QA gate, or automatic QC tri-review into a verification-only run. The scenario rows registered here are the legitimate exception to the "never a development plan's task" boundary inmstar-harness-core§ 定向执行与验证边界 — that boundary governs development plans, not this verification-only workflow. - PM dispatches ops. Use
Execute as: ops-engineer,Task category: ops,Delegation: forbidden, and the existing Scope / Inputs / Constraints / Evidence Required / Acceptance Criteria fields. Pass the concrete report path under{WORKFLOW_DIR}/<workflow-id>/reports/e2e.md. Ops executes only the named scenarios and records actual results usingreferences/report-template.md. - Run independent scenarios concurrently when sessions, devices, data, and writable state are isolated. Serialize shared state. Stop when the assigned scenarios finish; new environments or broader suites need matching user authorization.
- PM reviews the scoped report and closes.
InReviewmeans report acceptance against the scenario list, not another broad code review. Ops returns evidence and cannot mark Done. PM owns the final plan/workflow state and any bounded repair handoff; preserve the originating iteration's state and unit-test evidence.
What ships with it
1 file 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.
- 8d ago Changed 1b7ef4670fa3
- 9d ago Changed 19a68b3468cd
- 15d ago Changed · +2 lines ac3b027a828d
- 1mo ago Changed 3833fdc6602c
- 1mo ago First seen · 41 lines · 58 tokens per session scan A df8b1d9f8dab
mstar-e2e is a skill published in the GitHub repository btspoony/mstar-harness (63 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,057 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-09-13.
Other skills, from other repositories
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
qp
QP (Quality Platform) router — takes a web URL or a desktop app name and runs the plan → run → regress loop (qp-plan, qp-run, qp-regress) end to end, or routes to one stage. Classifies the target (public vs profile-required), probes which adapter the session has (Playwright MCP for web, computer-use MCP for desktop)…
qp-plan
Prepare stage of QP — builds a surface inventory of a web page or desktop app (routes, menus, forms, dialogs), checks it is MECE (no overlap, nothing missing that is visible), and designs test cases as a TSV with preconditions and expected values whose SOURCE is named. Works without a spec document (then expected…
qp-run
Automation stage of QP — executes the test cases from qp-plan against the live app through the session's adapter (Playwright MCP for web, computer-use MCP for desktop), records one verdict per step with a closed status, an MTM branch, whether the step was closed by machine evidence or left to judgment, and masks…
verify
A local, evidence-based procedure for checking that an implemented feature or bug fix works in the actual app. It uses a browser, test accounts, logs, and screenshots or command output rather than relying only on linting or type checks.
skillify
Codify the most recent successful /scrape flow into a permanent browser-skill on disk. (gstack).