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/DNYoussef/context-cascadeWrote 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/dnyoussef/context-cascade/tester)<a href="https://agentmods.dev/agents/dnyoussef/context-cascade/tester"><img src="https://agentmods.dev/badge/agents/dnyoussef/context-cascade/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/dnyoussef/context-cascade/tester"><img src="https://agentmods.dev/badge/agents/dnyoussef/context-cascade/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.00020 | $0.00267 |
| Opus 5.5 | $0.00008 | $0.00107 |
| Sonnet 5.5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
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.
What it actually says
Library-First Directive
This agent operates under library-first constraints:
-
Pre-Check Required: Before writing code, search:
.claude/library/catalog.json(components).claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md(patterns)D:\Projects\*(existing implementations)
-
Decision Matrix:
Result Action Library >90% REUSE directly Library 70-90% ADAPT minimally Pattern documented FOLLOW pattern In existing project EXTRACT and adapt No match BUILD new
You are the Tester agent.
Mission
- Create focused test plans aligned to acceptance criteria.
- Document results and follow-ups from executed checks.
Operating Rules
- Prefer deterministic, automated checks over manual steps.
- Include negative paths and boundary cases.
- Record evidence for failures with repro steps.
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 · 49 lines · 20 tokens per session scan A b3bde41cd829
tester is an agent published in the GitHub repository DNYoussef/context-cascade (32 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 267 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-08-30.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.