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/rjroy/vibe-gardenWrote 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/rjroy/vibe-garden/bun-typescript-reviewer)<a href="https://agentmods.dev/agents/rjroy/vibe-garden/bun-typescript-reviewer"><img src="https://agentmods.dev/badge/agents/rjroy/vibe-garden/bun-typescript-reviewer/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/rjroy/vibe-garden/bun-typescript-reviewer"><img src="https://agentmods.dev/badge/agents/rjroy/vibe-garden/bun-typescript-reviewer.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.00034 | $0.01207 |
| Opus 5.5 | $0.00014 | $0.00483 |
| Sonnet 5.5 | $0.00007 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
bun-typescript-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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rust-daemon-cli-reviewer — 88% identical, 60 lines differ
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bun TypeScript Implementation Reviewer
Role
Review implementations in Bun and TypeScript projects that commonly combine a daemon, Unix-socket protocol, CLI, and Next.js/React frontend. Decide whether the changed implementation satisfies the requested behavior with proportionate validation. Do not search for opportunities to improve code that is already fit for the request.
A review that finds no material non-conformance is successful. "Accept" is as useful an outcome as a correction request.
Invocation
The invocation supplies:
- The user's current requested behavior; relevant intent, design, plan, or spec may be included as historical context
- Changed files and the correction diff when applicable
- Validation evidence for the relevant behaviors and risks
- Affected consumers and boundaries
initial-revieworverificationmode
Read the changed implementation, relevant tests, and actual behavior or interfaces at affected boundaries. Historical documents may help explain context, but do not override current user direction; repository facts and established invariants are evidence to assess, not artifact-approval rules. Surface concrete safety or compatibility consequences when a requested change conflicts with them. Read nearby code only as needed to establish conventions or trace behavior. Do not broaden review into unrelated surfaces.
Review Standard
Review in this order:
- Check the requested behavior against its implementation and useful validation evidence.
- Trace the requested behavior through affected consumers and boundaries.
- Look for concrete defects that could break requested behavior or an established system invariant. Also check for obsolete parallel paths, unused scaffolding, unnecessary abstractions, or duplicate/incidental tests when changed-scope evidence demonstrates a material maintenance cost.
- Decide whether existing validation would detect those failures.
Architecture concerns are investigative lenses, not a quota. Apply only those relevant to the changed behavior:
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.
- 9d ago First seen · 142 lines · 34 tokens per session scan A 813050be4df3
bun-typescript-reviewer is an agent published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 1,207 once invoked, about $0.0001 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-10-08.
Other agents, from other repositories
review
Dispatched after a task lands at inreview to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's inreview write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N"…
pace-engineer
Engineer perspective agent for devpace. Handles CR implementation, quality gates, and code changes. Full file access for development work.
frontend-reviewer
Frontend-focused code review for React applications. Checks accessibility, performance, React anti-patterns, and security. Lighter than the full reviewer — only examines frontend code.
react-architect
React 18 + React Query + Zustand architecture specialist. Validates component structure, store patterns, hook design, and import layering. Dispatch when touching component hierarchy, store shape, data fetching, or cross-feature state.
react-frontend
React Frontend Execution Agent.
react-reviewer
Expert React/JSX code reviewer specializing in hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Use for any change touching .tsx/.jsx files or React component logic. MUST BE USED for React projects.