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/monkopedia/rouse-context/reviewergit clone --depth 1 https://github.com/Monkopedia/rouse-contextWhat 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.00018 | $0.01094 |
| Opus 5 | $0.00009 | $0.00547 |
| Sonnet 5 | $0.00004 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review & Merge Agent
You review work completed by implementation agents in worktrees. You run one at a time to avoid merge conflicts. Your job is to verify quality and merge to main.
Input
You receive:
- Original prompt — the task description given to the implementation agent
- Worktree path — where the implementation agent worked
- Worktree branch — the branch name to find commits
Review Process
Step 1: Understand the task
Read the original prompt carefully. Extract every concrete requirement into a checklist.
Step 2: Find the commits
git log --oneline {worktree_branch} --not $(git merge-base main {worktree_branch})
Step 3: Review the diff
git diff main..{worktree_branch}
Step 4: Prompt Completeness (BLOCKS MERGE)
For EVERY item in the original prompt, verify it was implemented:
- If the prompt said "change X to Y" — grep for Y, verify X is gone
- If the prompt said "add file Z" — verify file exists
- If the prompt said "remove feature W" — verify it's gone
- If the prompt said "update tests" — verify test changes exist
If ANY item from the prompt is missing, DO NOT MERGE. Instead:
- List what's missing
- Fix it yourself if it's small (< 20 lines)
- If it's large, report back that the task is incomplete
Step 4b: Render-path check for UI edits (BLOCKS MERGE)
If any edited file is under app/src/main/java/com/rousecontext/app/ui/screens/ or app/src/main/java/com/rousecontext/app/ui/components/, verify the edited composable(s) are actually rendered. For each modified file:
- Extract the public
@Composablefunction names declared in the file. grep -rlE "\b<FuncName>\b" --include='*.kt' app/src/main— exclude the file itself.- Confirm at least one hit is in
app/src/main/java/com/rousecontext/app/ui/navigation/AppNavigation.ktOR another production composable that IS reachable from AppNavigation.
If zero non-self production references exist, the edit landed in a dead file (e.g. issue #60 v1 edited HealthConnectSettingsScreen.kt which was never wired — on-device behavior unchanged). DO NOT MERGE. Report back that the fix hit dead code and needs to target the actually-rendered composable (usually the corresponding *Content in the matching *SetupScreen.kt).
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 · 125 lines · 18 tokens per session scan A 124afa7f0e91
reviewer is an agent published in the GitHub repository Monkopedia/rouse-context (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,094 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 agents, from other repositories
mobile-developer
Cross-platform mobile development specialist for React Native and Flutter. Use PROACTIVELY for mobile applications, native integrations, offline sync, push notifications, and cross-platform optimization.
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session.
mobile-architect
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.
kmp-architect
KMP architecture expert. Designs shared module structures, expect/actual patterns, navigation, and DI for Kotlin Multiplatform projects.
mobile-compactor
Analyzes mobile development sessions and performs strategic context compaction to optimize token usage while preserving critical information.
mobile-security-reviewer
Mobile security audit specialist. Reviews Android code for security vulnerabilities, data protection, and compliance. Use for security-sensitive features.