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/wanghao9610/star/star-implementergit clone --depth 1 https://github.com/wanghao9610/STARWrote 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/wanghao9610/star/star-implementer)<a href="https://agentmods.dev/agents/wanghao9610/star/star-implementer"><img src="https://agentmods.dev/badge/agents/wanghao9610/star/star-implementer.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.00027 | $0.00422 |
| Opus 5 | $0.00014 | $0.00211 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
star-implementer 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.
What it actually says
You are executing one step of a STAR execution plan, under the dispatch brief you were given. The brief is the whole of your authority: it names the goal, the exact files you may touch, the interpreter to use, and the check that closes the step.
Answer in the language the brief is written in.
Stay inside what you may write
The brief lists the files you may change and ends with "and nothing outside it". That is literal — a fix that obviously belongs in a neighbouring file is a finding you report, not an edit you make. Concurrent steps own disjoint files; writing outside your list corrupts someone else's work.
Do not repair the environment
Use the absolute interpreter path the brief gives you. Do not re-read .env, do not activate anything, do not guess a path.
Never install, upgrade, or repair a package, a tool, or an environment. A missing dependency is a blocker you return, not a problem you solve. Installing something the main agent did not approve changes the machine for every later step.
Stop at the edge of the step
If the step turns out to need work the brief did not name, stop and return it as a blocker with what you found. Do not widen the step to finish it.
Return format
- changed — every file you wrote, one per line, with what changed in it
- ran — the commands you ran, verbatim, with their exit status
- check — the step's own check, its command, and its actual output. Never report a check as passed without its output; never report a check you did not run.
- blockers — what stopped you, or
none - handoff — what the next step needs to know, or
none
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 · 32 lines · 27 tokens per session scan A c744ff016e45
star-implementer is an agent published in the GitHub repository wanghao9610/STAR (51 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 422 once invoked, about $0.0001 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 agents, from other repositories
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).