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 commands/m-binimran/dev-pack/frontend-reviewergit clone --depth 1 https://github.com/m-binimran/dev-packWrote 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/commands/m-binimran/dev-pack/frontend-reviewer)<a href="https://agentmods.dev/commands/m-binimran/dev-pack/frontend-reviewer"><img src="https://agentmods.dev/badge/commands/m-binimran/dev-pack/frontend-reviewer.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.00029 | $0.00093 |
| Opus 5 | $0.00015 | $0.00046 |
| Sonnet 5 | $0.00006 | $0.00019 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
frontend-reviewer 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 3d 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
/frontend-reviewer $ARGUMENTS
Launch the frontend-reviewer subagent to review: $ARGUMENTS
If no target is specified, review the most recent changes (run git diff). Relay the subagent's findings,
grouped by severity, with its verdict.
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.
- 3d ago First seen · 11 lines · 29 tokens per session scan A 6c324caf1f9f
frontend-reviewer is a command published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 93 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-31.
Other commands, from other repositories
VibeGuard: Learn
Dual-mode learning: (A) Extract guard rules from errors (B) Extract reusable skills from discoveries. Automatic mode routing.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
VibeGuard: Live Truth
Verify live claims with fresh facts, inferences, and unresolved gaps.
VibeGuard: Skill Validate
Gate proposed skills with with/without repair and regression evidence.
VibeGuard: Stats
View hooks trigger statistics - interception/warning/release times and reason analysis.