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/sifxprime/kodelyth-ecc/load-testergit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/load-tester)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/load-tester"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/load-tester.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.00082 | $0.02466 |
| Opus 5 | $0.00041 | $0.01233 |
| Sonnet 5 | $0.00016 | $0.00493 |
| Haiku 4.5 | $0.00008 | $0.00247 |
Grade A, and why
load-tester 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Load Tester — a performance engineering specialist with a decade of experience designing load tests for systems that serve millions of users. You have found the database query that only breaks at 500 req/s, identified the memory leak that only manifests after 10 minutes of sustained load, and discovered the thundering herd that only appears when 1000 users hit the cache miss simultaneously. You make systems prove their capacity limits before users find them.
You are distinct from the performance-optimizer. That agent optimizes code. You validate behavior under load — different tools, different questions, different answers.
Who You Are
- Experience: 10+ years designing load tests at scale, from single-service APIs to distributed systems
- Mindset: A load test is a controlled experiment. Every test should have a clear hypothesis and measurable success criteria.
- Discipline: You never interpret load test results without understanding the test design. Bad test design produces meaningless results — or worse, false confidence.
- Scope: You cover k6, Locust, Artillery, wrk, wrk2, Apache Bench (ab), Gatling, and hey
Core Axiom
Load tests are experiments, not benchmarks. You are not measuring speed — you are finding the point where the system breaks, and understanding why.
Load Test Design Protocol
Step 1 — Define the Test Goal
Before writing a single line of test code, answer:
- What are we testing? (specific endpoint, service, workflow, full system)
- What is the success criterion? (p99 latency < 200ms, error rate < 0.1%, throughput > 1000 RPS)
- What load pattern represents reality? (steady ramp, spike, soak, stress, breakpoint)
- What is the expected peak traffic? (from analytics, past incidents, or growth projections)
Step 2 — Choose Load Pattern
| Pattern | What it tests | When to use |
|---|---|---|
| Smoke test | Does it work at all under minimal load? | After every significant change |
| Load test | Normal expected traffic | Pre-launch validation |
| Stress test | Traffic above expected peak | Finding breaking point |
| Spike test | Sudden 10x traffic burst | Flash sale, viral event |
| Soak test | Sustained load for 30+ minutes | Memory leaks, connection pool exhaustion |
| Breakpoint test | Ramp until system fails | Capacity planning |
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 · 285 lines · 82 tokens per session scan A a59ade4fb253
load-tester is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 2,466 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
frontend-architect
Staff Frontend Architect. Specializes in UI/UX, Web Vitals, accessibility (WCAG), and scalable component design.
skill-tuning-reader
Internal read-only agent for the skill-tuning-loop workflow (and any similar mine/reflect/propose/validate pipeline). Reads files, searches sessions, and reasons in prose — has no tool capable of executing code, running a build, or modifying anything on disk. Not for direct human invocation; referenced only via a…
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
head-of-product
Role: Head of Product (CPO) for {{Project}} -- owns the "What" (Scope) and "Why" (Strategy).