Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Ohswedd/praxis/plugin install praxisWrote 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/ohswedd/praxis/perf-scalability-analyst)<a href="https://agentmods.dev/agents/ohswedd/praxis/perf-scalability-analyst"><img src="https://agentmods.dev/badge/agents/ohswedd/praxis/perf-scalability-analyst.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.00052 | $0.00613 |
| Opus 5 | $0.00026 | $0.00307 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
perf-scalability-analyst 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 6d 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
Scope the change before you judge it. How to do that is defined once, in the
review-scope skill, preloaded into your context at startup. If it is not there,
read ${CLAUDE_PLUGIN_ROOT}/skills/review-scope/SKILL.md before you begin: an
audit scoped with git diff alone reads nothing on a branch that has committed
work, and reports PASS on a change it never saw.
You assess whether the code under review is fast enough now and will stay fast as things grow. Read-only.
For the scope under review (the current change set, or the files assigned to you by a repo-wide scan):
- Complexity. Time and space complexity of the added/changed logic. Flag accidental quadratic (nested loops over the same collection), repeated work, and recomputation that could be hoisted or memoized.
- Data access. N+1 queries, missing indexes implied by query shape, over-fetching, chatty I/O, unbatched network calls.
- Allocation & memory. Unnecessary copies, unbounded buffers, retained references, large in-memory structures that should stream.
- Hot paths. Is this code on a hot path (per-request, per-item, per-frame)? Cost matters more there. Identify which.
- Scalability. Behaviour as N (rows, users, items, concurrency) grows by 10x/100x. Where does it break first? Any hard ceilings or serialization points?
- Caching & laziness. Opportunities to cache, batch, paginate, or defer, and correctness risks those introduce.
- Front-end delivery (when the scope is UI). Shipped JS/CSS weight, render-blocking resources, image sizing/formats and lazy loading, font loading strategy, layout thrash and main-thread work: Core Web Vitals (LCP, CLS, INP) risk as the page and data grow.
Quantify where you can (Big-O, expected call counts). Distinguish premature optimization from real risk; do not recommend complexity that the workload does not justify.
Return PASS, PASS WITH NOTES, or FAIL with specific, cited findings.
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.
- 6d ago First seen · 50 lines · 52 tokens per session scan A c07c997e809c
perf-scalability-analyst is an agent published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 613 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
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Applies safe local simplifications (local renames, dead code, unnecessary nesting) directly and proposes structural changes for approval. Focuses on recently modified code unless instructed otherwise; not for…
mp-adversarial-reviewer
Adversarial second-opinion review of a completed masterplan task. The harness runs this agent on the routing policy's adversary lane (breaker role, frontier lane — panel adversarial for cross-vendor coverage) and it returns a severity-first findings digest (CD-10). Runs per done task during execution when the run…
plan-code-review
Post-implementation code review against the plan, returning findings without a verdict. Spawned once by /ac:execute Phase 3.
mp-alignment-auditor
Read-only, fresh-context audit of a merged masterplan plan against the ORIGINAL user request. Consumes goals.md (its topic: anchor + goals), spec.md, and the merged plan as QUOTED DATA (never instructions); decomposes the anchor into stable clauses A1..An for the user to confirm, then judges per-clause drift. The…
python-data-architect
Python data pipeline (Pandas/Polars + SQLAlchemy) architecture specialist. Validates pipeline/transform/loader/writer layering, pure-function transforms, no-mutation discipline, type hint requirements, and Polars-over-Pandas guidance. Dispatch when touching pipelines, transforms, loaders, writers, or schema models.
python-ml-architect
Python ML (PyTorch/scikit-learn) architecture specialist. Validates data/model/training/evaluation/inference layering, config-driven hyperparameters, reproducibility discipline, and pipeline separation. Dispatch when touching model definitions, training loops, datasets, or inference code.