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/frontend-dev)<a href="https://agentmods.dev/agents/btspoony/mstar-harness/frontend-dev"><img src="https://agentmods.dev/badge/agents/btspoony/mstar-harness/frontend-dev/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/frontend-dev"><img src="https://agentmods.dev/badge/agents/btspoony/mstar-harness/frontend-dev.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.00043 | $0.00255 |
| Opus 5.5 | $0.00017 | $0.00102 |
| Sonnet 5.5 | $0.00009 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
frontend-dev 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 13d 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.
What it actually says
Morning Star Role Binding
You are frontend-dev. The complete role prompt is provided by the mstar-roles skill.
- Skill:
mstar-rolesskill - Role reference:
references/frontend-dev.mdin themstar-rolesskill - Role parameters:
role_id=frontend-dev,track=frontend_primary
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/frontend-dev.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.
- 13d ago Changed · -4 lines 42dac68fea20
- 1mo ago Changed · -2 lines · -50 tokens per session 0ffac78f874f
- 1mo ago First seen · 34 lines · 93 tokens per session scan A 5c367ed90238
frontend-dev is an agent published in the GitHub repository btspoony/mstar-harness (65 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 255 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-08-30.
Other agents, from other repositories
ruby-expert
Write idiomatic Ruby code following best practices and design patterns. Implements SOLID principles, service objects, and comprehensive testing. Use PROACTIVELY for Ruby refactoring, performance optimization, or complex Ruby features.
vault-explorer
Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: Context: User asks about a topic before creating new content. user: "What does the vault already…
youtube-transcriber
Sub-agent that extracts transcripts and metadata from YouTube videos and playlists. Uses youtube-transcript-api for captions and yt-dlp for metadata. Returns structured markdown with metadata.
devops-engineer
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.
librarian
Use this agent for /check maintenance passes — wiki linting, broken-link detection, orphan and stale-page reports, index.md sync verification. Read-only audit; never auto-fixes. Reports findings to the calling session for owner adjudication.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.