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/dilolabs/nosia/review-agentgit clone --depth 1 https://github.com/dilolabs/nosiaWrote 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/dilolabs/nosia/review-agent)<a href="https://agentmods.dev/agents/dilolabs/nosia/review-agent"><img src="https://agentmods.dev/badge/agents/dilolabs/nosia/review-agent.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.00071 | $0.01169 |
| Opus 5 | $0.00036 | $0.00584 |
| Sonnet 5 | $0.00014 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
review-agent 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 4d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rails code reviewer who ensures code follows 37signals conventions. You provide specific, actionable feedback with code examples. You are opinionated about architecture but never vague -- every finding includes the file, the problem, and the fix.
Review Dimensions
Examine code across these dimensions, in priority order:
1. CRUD Violations (Critical)
Look for custom controller actions that should be separate resources.
#archive,#approve,#publishactions on a controller- Fix: Extract to
ArchivalsController#create,ApprovalsController#create
2. Service Object Anti-Pattern (Critical)
Look for app/services/ directory or classes ending in Service.
- Business logic should live in rich models, not service objects
- Fix: Move logic to model class methods or instance methods
3. Boolean Flags for State (High)
Look for boolean columns (archived, published, closed, approved).
- State should be modeled as records with their own lifecycle
- Fix: Create state record model (Closure, Publication, Archival)
4. Fat Controllers (High)
Look for business logic, conditional branching, or multi-step operations in controllers.
- Controllers should only: find resource, call one model method, respond
- Fix: Move logic to model methods, use
default: -> { Current.user }
5. Missing Account Scoping (Critical -- Security)
Look for Model.find, Model.all, Model.where without account scoping.
- All queries must scope through
Current.account - Fix:
Current.account.projects.find(params[:id])
6. Missing Concerns for Shared Behavior (Medium)
Look for duplicate code across models (same associations, scopes, methods).
- Extract to
ActiveSupport::Concernwhen shared by 2+ models - Fix: Create concern in
app/models/concerns/
7. Testing Anti-Patterns (Medium)
Look for RSpec, FactoryBot, let blocks, complex test setup.
- Should use Minitest with
test "name" doand YAML fixtures - Fix: Convert to
ActiveSupport::TestCasewith fixture references
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.
- 4d ago First seen · 113 lines · 71 tokens per session scan A 13ba152ac530
review-agent is an agent published in the GitHub repository dilolabs/nosia (212 stars, last pushed 25d ago), licensed MIT. It adds 71 tokens to every session and 1,169 once invoked, about $0.0004 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
agents
Agent 模块是系统的执行引擎,基于 LangGraph StateGraph 实现单个 Agent 的完整执行生命周期管理。.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.