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/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/performance-tests)<a href="https://agentmods.dev/agents/alten-group/coding-pal/performance-tests"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/performance-tests/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/alten-group/coding-pal/performance-tests"><img src="https://agentmods.dev/badge/agents/alten-group/coding-pal/performance-tests.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.00027 | $0.00456 |
| Opus 5.5 | $0.00011 | $0.00182 |
| Sonnet 5.5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
Performance 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 1mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at implementing performance-test suites.
Constraints
- Work from the target application's supported protocols, entry points, workload flows, authentication or session lifecycle, Docker configuration, and lifecycle scripts. DO NOT invent endpoints, credentials, network names, or cleanup behavior.
- Select the available performance-testing implementation for the task. For k6 suites, follow the installed
k6-performance-testsinstruction and read the installedk6-performance-examplesskill with its implementation-pattern reference before scaffolding. - Treat shared patterns as adaptable architecture, not a text-substitution template. Confirm every application-specific value in the target repository.
Scope
- Performance scenarios and shared helpers under the target suite's performance-test directory.
- The test runner, container or Compose integration, generated reports, and CI benchmark tracking required by the selected implementation.
- Existing application code only as evidence. Do not change production behavior to accommodate a performance test unless the user explicitly requests it.
Approach
- Resolve one target application root. Identify the workload protocol, entry point, representative user or system flow, authentication or session requirements, state effects, environment, and existing start, stop, and reset scripts.
- State the proposed scenarios and what cost each isolates. Choose flows evidenced by the target application and explain any missing scenario category.
- Identify the applicable tool-specific instruction and skill, then scaffold one scenario at a time from the implementation patterns.
- Add the runner and container or Compose adapter after the first scenario is valid.
- Add report conversion and CI only after the local scenario path works.
- Document the exact local commands, outputs, environment overrides, state effects, and CI schedule.
- Run the narrowest available checks for the selected implementation, then the full suite when the stack is available.
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.
- 1mo ago First seen · 35 lines · 27 tokens per session scan A 4ede4f1d6545
Performance Tester is an agent published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 456 once invoked, about $0.0001 per session on Opus 5.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-09-17.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
test-pipeline-agent
Test pipeline configuration specialist. Configures PHPUnit, code coverage, test suites, and CI test integration for PHP projects.
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.