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/talayash/agentrium/review-prgit clone --depth 1 https://github.com/talayash/agentriumWrote 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/talayash/agentrium/review-pr)<a href="https://agentmods.dev/commands/talayash/agentrium/review-pr"><img src="https://agentmods.dev/badge/commands/talayash/agentrium/review-pr.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.00000 | $0.00292 |
| Opus 5 | $0.00000 | $0.00146 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
review-pr 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
Review a pull request
Review the PR at $ARGUMENTS (a PR number or URL). Fetch the diff and changed files, then check for:
Rust Backend
- No
.unwrap()in production code paths - use.map_err()or?operator - Proper
Arc<Mutex<>>usage for shared state access - PTY reader threads properly handle process exit
CREATE_NO_WINDOWflag used for spawned processes on Windows- All
#[tauri::command]handlers returnResult<T, String>
React Frontend
- xterm.js
Terminalinstances are disposed on unmount - Tauri event listeners return unlisten functions that are called on cleanup
- No stale closures in Zustand selectors or useEffect hooks
- Consistent dark glassmorphic Tailwind classes
IPC Consistency
- Every new
invoke()call has a matching registered command inmain.rs - Parameter names and types match between Rust and TypeScript
- Error handling uses try/catch around invoke calls
General
- No new capabilities added to
capabilities/default.jsonwithout justification - Version numbers consistent across
package.json,Cargo.toml,tauri.conf.json - No secrets or credentials committed
Provide a summary with findings grouped by severity (blocking, warning, nit).
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 · 29 lines · 0 tokens per session scan A b46c5bceae7f
review-pr is a command published in the GitHub repository talayash/agentrium (39 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 292 tokens. 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 commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
validate-gap
Analyze implementation gap between requirements and existing codebase.
spec-impl
Execute spec tasks using TDD methodology.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
design-review
Review UI changes against the paper-mono design rules. Requires a screenshot or running pnpm tauri dev for render-time checks.