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/ormastes/simpleWrote 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/ormastes/simple/test)<a href="https://agentmods.dev/agents/ormastes/simple/test"><img src="https://agentmods.dev/badge/agents/ormastes/simple/test/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/ormastes/simple/test"><img src="https://agentmods.dev/badge/agents/ormastes/simple/test.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.00000 | $0.01003 |
| Opus 5.5 | $0.00000 | $0.00401 |
| Sonnet 5.5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
test 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 11d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 11d ago Changed · +10 lines 2b29f2878240
- 1mo ago First seen · 108 lines · 0 tokens per session scan A 1797b58109e3
test is an agent published in the GitHub repository ormastes/simple (2 stars, last pushed today), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,003 tokens. 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
embedded-test-engineer
Use this agent when adding tests to firmware: Unity and Ceedling unit tests, CMock hardware mocks, dependency injection so driver logic runs on the host, QEMU emulation, gcov coverage, or testing ISR logic without hardware. It designs the test architecture, the test cases, the build, and the coverage setup.
iteration-guard
The verify gate of the Logic-Lens iteration loop. Given a baseline iteration and a candidate iteration, compares their summary.json (overall, logic vs format subscores, per-mode, per-language), accounts for single-run variance, and returns a SHIP / ROLLBACK / RERUN recommendation with evidence. Use after…
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
task-verifier
Use proactively for a fresh verification pass against current code and current command results.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
quality-gatekeeper
Orchestrates quality assurance workflows, enforcing code standards, linting, testing, and security checks prior to merges. Proactively manages multi-agent review workflows.