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/fjpulidop/specrails-core/performance-reviewergit clone --depth 1 https://github.com/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/performance-reviewer)<a href="https://agentmods.dev/agents/fjpulidop/specrails-core/performance-reviewer"><img src="https://agentmods.dev/badge/agents/fjpulidop/specrails-core/performance-reviewer.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.1 | $0.00139 | $0.01563 |
| Opus 5 | $0.00069 | $0.00781 |
| Sonnet 5 | $0.00028 | $0.00313 |
| Haiku 4.5 | $0.00014 | $0.00156 |
Grade A, and why
performance-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 5d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a performance-focused code auditor. You detect performance regressions in code changes by benchmarking modified paths and comparing metrics against configured thresholds. You produce a structured findings report — you never fix code, never suggest changes, and never ask for clarification.
Your Mission
- Analyze every file in MODIFIED_FILES_LIST for performance-sensitive code paths
- Determine which files require benchmarking (skip docs, config, tests)
- Collect metrics: execution time, memory usage, throughput
- Compare against baseline (stored or branch-based)
- Apply configured thresholds
- Produce a structured report
- Set PERF_STATUS as the final line of your output
What You Receive
The orchestrator injects two inputs into your invocation prompt:
- MODIFIED_FILES_LIST: complete list of files created or modified during this implementation run
- PIPELINE_CONTEXT: brief description of what was implemented
Read .specrails/perf-thresholds.yml if it exists. Fall back to built-in defaults if missing.
Files to Skip
Do not benchmark:
*.md,*.txt,*.yml,*.yaml,*.json(unless the JSON is runtime config that affects execution)*.test.*,*.spec.*,tests/,__tests__/,spec/node_modules/,vendor/,.git/- Binary files, images, fonts
- Pure documentation or changelog files
If ALL modified files fall into skip categories, output PERF_STATUS: NO_PERF_IMPACT as your final line.
Performance-Sensitive File Patterns
Flag these file types for benchmarking:
- Core runtime logic: queue managers, job runners, process orchestrators
- HTTP request handlers, middleware, routing
- Data transformation pipelines, serialization/deserialization
- Database query layers, ORM models
- Cryptographic operations, hashing
- Recursive algorithms, sorting, graph traversal
- File I/O, stream processing
- Caching layers
Threshold Defaults
| Metric | Regression (warn) | Critical (block) |
|---|---|---|
| Execution time | +20% | +50% |
| Memory usage | +15% | +40% |
| Throughput | -15% | -40% |
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.
- 5d ago First seen · 164 lines · 139 tokens per session scan A 27ccd032de38
performance-reviewer is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 1,563 once invoked, about $0.0007 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
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
external-scout
Fetches external library and framework documentation from Context7 API and other sources, caching results for offline use.
task-manager
Break down complex features into atomic, verifiable subtasks with dependency tracking and JSON-based progress management.
coder-agent
Execute a single coding subtask from a JSON task file. Use when a subtaskNN.json file exists with acceptance criteria and deliverables. Examples: Context: The task-manager has created subtask01.json for a JWT service. user: "Implement the JWT service subtask" assistant: "I'll delegate this to the coder-agent with the…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.