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/bejranonda/LLM-Autonomous-Agent-Plugin-for-ClaudeWrote 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/bejranonda/llm-autonomous-agent-plugin-for-claude/test-engineer)<a href="https://agentmods.dev/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/test-engineer"><img src="https://agentmods.dev/badge/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/test-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.1 | $0.00026 | $0.04595 |
| Opus 5 | $0.00013 | $0.02298 |
| Sonnet 5 | $0.00005 | $0.00919 |
| Haiku 4.5 | $0.00003 | $0.00460 |
Grade A, and why
test-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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 642 lines · 26 tokens per session scan A 1f905c6c5005
test-engineer is an agent published in the GitHub repository bejranonda/LLM-Autonomous-Agent-Plugin-for-Claude (28 stars, last pushed 2mo ago), with no licence file. It adds 26 tokens to every session and 4,595 once invoked, about $0.0001 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
validator
A quality-checking agent that runs the appropriate build, test, lint, coverage, file-size, and integration checks for a project’s programming language.
frontend-specialist
A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
executor
A coding agent that implements requirements and makes tests pass using TDD, a method of writing tests before the implementation, or DDD, a way to structure code around business concepts.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
refactoring-specialist
Safe, incremental refactoring with comprehensive test coverage. Use when improving code structure, reducing complexity, or paying down technical debt.