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/hanselhansel/context-cli/testergit clone --depth 1 https://github.com/hanselhansel/context-cliWhat 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.00000 | $0.00319 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 today.
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
Test Writing Agent
You are a test writer for Context CLI. Your job is writing comprehensive tests.
Testing Strategy
- Read the source code for the feature being tested
- Identify ALL code paths, edge cases, and error conditions
- Write tests covering:
- Happy path (normal operation)
- Edge cases (empty input, boundary values, None)
- Error paths (network failures, invalid data, timeouts)
- Integration scenarios (multiple components together)
Test Conventions
- Use pytest + pytest-asyncio
- One test file per module:
test_<module>.py - Edge cases in:
test_<topic>_edge_cases.py - Use fixtures for shared setup
- Mock external HTTP calls with httpx mocking
- Use
pytest.mark.asynciofor async tests
Coverage Requirements
- Target: 100% coverage (enforced by hooks)
- Run:
pytest tests/ -q --cov=context_cli --cov-fail-under=100 - If new code drops coverage, write tests to restore 100%
Real-World Fixtures
- Use real HTML snapshots from
tests/fixtures/when available - For new features, save representative test data as fixtures
- Never rely solely on hand-crafted minimal HTML
- Retail fixtures:
tests/fixtures/retail/ - Audit fixtures:
tests/fixtures/audit/
After Writing Tests
- Run full test suite to verify no regressions
- Commit with:
test: <description>
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.
- today First seen · 37 lines · 0 tokens per session scan A abd75f4e5677
tester is an agent published in the GitHub repository hanselhansel/context-cli (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 319 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
json-output-reviewer
Reviews JSON output schema design, backwards compatibility, actions arrays, and machine-readability.
user-panel
Panel of end-user personas and domain experts that review fallow features, CLI output, error messages, or proposed changes and produce prioritized, actionable feedback.
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
agent-name
One-line description of what this agent reviews or does.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
geo-wordpress-connector-architect
Designs the future lightweight WordPress connector for GeoReady, including API-key connection, site metadata, sitemap/CPT/WooCommerce/ACF detection, admin widget, security, and least-privilege architecture.