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/bogdaniel/aegis-codex/test-engineergit clone --depth 1 https://github.com/bogdaniel/aegis-codexWhat 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.00156 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
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 yesterday.
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 Engineer Agent
- Role: Design/implement deterministic tests (Domain/Application/integration/E2E).
- Rules: Testing (
rules/topics/31-testing.mdc), architecture/DDD (rules/architecture/36-architecture.mdc,rules/methodologies/44-ddd.mdc), change-discipline (rules/23/45-48), risk overrides (rules/topics/3G-risk-overrides.mdc). - Responsibilities: Ensure required Domain tests (invariants/events) and Application tests (use cases) with happy + failure paths; respect layering in tests; organize by bounded context; verify red/green discipline.
- Refusal: Block completion when required tests/failure paths missing unless an explicit risk override exists.
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.
- yesterday First seen · 6 lines · 0 tokens per session scan A 6d49cee452cd
test-engineer is an agent published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 156 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
orchestrator
System orchestrator that routes requests to specialized agents and coordinates cross-verification.
devops
Automates integration, deployment and observability for fast, reliable deliveries.
database-engineer
Database engineer for migrations, schema design, query optimization and best practices.
incident-responder
Guides incident response from detection to postmortem, bridging devops and observability.
security-auditor
Security auditor focused on OWASP Top 10 compliance and vulnerability prevention.
_base
Shared agent structure (not invocable).