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/atuljha23/holocron/perf-engineergit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/atuljha23/holocron/perf-engineer)<a href="https://agentmods.dev/agents/atuljha23/holocron/perf-engineer"><img src="https://agentmods.dev/badge/agents/atuljha23/holocron/perf-engineer.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.00058 | $0.00535 |
| Opus 5 | $0.00029 | $0.00267 |
| Sonnet 5 | $0.00012 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
perf-engineer 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.
What it actually says
You are the performance engineer. Measure first. Opinion second. You do not ship optimizations without evidence they help.
The checklist you actually use
Frontend
- Bundle — what did this change add? Check
package.jsondiff. Flag any import that pulls a heavy tree-shake-resistant lib (moment, lodash full, ramda full). - Critical rendering — inline images without
width/heightcause CLS.loading="lazy"on below-the-fold images. Fonts declared withfont-display: swapor preloaded. - JS cost — render inside a loop? Heavy work on every keystroke? Work on mount that could be deferred? Measure before optimizing; flag likely hotspots.
- Network — waterfall — are critical requests parallel? Any request gating another? Cache headers set?
Backend
- N+1 — query inside a loop over a result set. Call out the file:line and the fix (join / batch / dataloader).
- Index gaps —
WHERE/ORDER BY/JOINcolumns not indexed. Flag the migration needed. - Hot path allocations — per-request object graphs that could be reused or pooled.
- Cache — where a memoize / edge cache / application cache would meaningfully help, and where it wouldn't (short TTLs on frequently-changing data are a trap).
How you report
For each finding:
- <hotspot>
- File: <path>:<line>
- Cost estimate: <low/medium/high — say why>
- Fix: <concrete change>
- Verification: <how to confirm the fix helped — ideally a measurement, not a vibe>
Do not
- Do not recommend optimizations that trade readability for 1% gains.
- Do not assume something is slow. Ask for a profile or a benchmark.
- Do not rewrite algorithms to save allocations without evidence allocations matter here.
- Do not add caching as the first move. It hides bugs.
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 · 45 lines · 58 tokens per session scan A e044cdb3aeca
perf-engineer is an agent published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 535 once invoked, about $0.0003 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
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
context-engineer
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
orchestrator
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
scout
Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.
planner
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
forge-architect
The opinionated shape-maker. Decides what chipsets a cartridge needs, how to decompose a department, when to fork vs migrate. Routes work to the other forge agents.