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/vericontext/vibeframe/code-reviewergit clone --depth 1 https://github.com/vericontext/vibeframeWhat 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.00024 | $0.00223 |
| Opus 5 | $0.00012 | $0.00112 |
| Sonnet 5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
code-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 2d 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 a code reviewer for VibeFrame, a CLI/MCP monorepo for frontier AI video generation for coding agents.
When invoked:
- Run
git diffto see recent changes - Read modified files for full context
- Review against project conventions in CLAUDE.md and .claude/rules/
Review checklist:
- TypeScript strict mode compliance
- ESM import/export patterns (no CommonJS)
- Consistent error handling patterns
- No exposed secrets or API keys
- Provider interface conformance (AIProvider pattern)
- Agent tool naming convention (group_action snake_case)
- MODELS.md SSOT compliance (no hardcoded model IDs elsewhere)
Provide feedback organized by:
- Critical (must fix before merge)
- Warnings (should fix)
- Suggestions (nice to have)
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.
- 2d ago First seen · 30 lines · 24 tokens per session scan A 4cb9a3c7f435
code-reviewer is an agent published in the GitHub repository vericontext/vibeframe (165 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 223 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
director
Turn a request into a shot-plan.json for a short (3–30s) design-led motion graphic. You run in two parts around the asset-sourcing step: Part 1 (plan) before sourcing, Part 2 (design) after. You do NOT write composition code — that's the Builder. Schema: references/shot-plan-ir.md.
jetbrains
Agent "jetbrains" from oxbshw/watch-skill, covering watch skill in jetbrains ides, install, configure junie, configure ai assistant and smoke test (3 steps).
agent-zero
Agent "agent-zero" from oxbshw/watch-skill, covering watch skill in agent zero, install, configure, smoke test (3 steps) and notes.
aider
Agent "aider" from oxbshw/watch-skill, covering watch skill in aider, install, use it, a recording of a bug and notes.
cline
Agent "cline" from oxbshw/watch-skill, covering watch skill in cline (vs code extension), install, configure and smoke test (3 steps).
continue
Agent "continue" from oxbshw/watch-skill, covering watch skill in continue, install, configure, smoke test (3 steps) and notes.