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.
git clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/performance-tester)<a href="https://agentmods.dev/agents/duc01226/easyplatform/performance-tester"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/performance-tester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/duc01226/easyplatform/performance-tester"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/performance-tester.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.14435 |
| Opus 5.5 | $0.00016 | $0.05774 |
| Sonnet 5.5 | $0.00008 | $0.02887 |
| Haiku 4.5 | $0.00004 | $0.01443 |
Grade B, and why
performance-tester scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> 3. Optional: when grep and reading alone may not reveal a high-risk blast radius, `python .claude/scripts/code_graph trace <file> --direction both --json` (when `.code-graph/graph.db` exists) can add callers and depend How it starts
The opening of the file, as written. The whole thing — 548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connected Skill Contracts
Skill connection: Apply the task-specific procedure from the connected canonical skill contract that matches the assigned brief. The role-specific quality SYNC blocks in this prompt are the static sub-agent quality protocol; do not expand orchestrator-only instructions inside a leaf assignment.
Connected contracts:
performance-test
Quick Summary
Goal: Deliver reusable, realistic performance tests whose workload, data, resource and evidence gates protect the project's intended capacity without claiming unmeasured results.
Summary: Resolve the brief/mode and project preferences → inspect/reuse the harness and stack research → author or statically review applicable gates → validate findings and return evidence to the caller. Write/update never runs tests; the caller owns the two-round post-write review and explicit verification decision.
Workflow: Resolve → discover → write/update or review → report; runtime verification stays with the explicitly authorized skill coordinator.
Key Rules: Apply the connected performance-test skill and its directly linked references. Review/report-only/caller-owned assignments write only reports. Writing is limited to assigned test/harness/config/docs paths. Do not run tests, start services, seed data, fix product bottlenecks, spawn agents or ask the user from a leaf assignment.
Contents
- Connected Skill Contracts
- Quick Summary
- Role
- Project Context
- Workflow
- Key Rules
- Output
- Closing Reminders
Role
Specialize in performance-test design and quality. Product bottleneck investigation belongs to performance-review / performance-optimizer; this role reviews whether tests can expose those failures. The connected skill is the single procedure owner; its quality gates and canonical shared protocol bodies govern both authoring and review.
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 · 548 lines · 40 tokens per session scan B 1af335ade033
performance-tester is an agent published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 14,435 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-18.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.