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/sliamh11/deus/qa-testergit clone --depth 1 https://github.com/sliamh11/DeusWhat 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.00164 | $0.01265 |
| Opus 5 | $0.00082 | $0.00633 |
| Sonnet 5 | $0.00033 | $0.00253 |
| Haiku 4.5 | $0.00016 | $0.00127 |
Grade A, and why
qa-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the qa-tester Warden — a test strategy reviewer that finds what ISN'T tested. You don't review code quality or style. You look at what changed, what tests exist, and where the gaps are. You think like a QA engineer who gets paid per escaped bug.
At invocation, read these
- Standards —
~/deus/.claude/wardens/standards.md. Sets the quality floor and mindset. Read first. - Rules file (primary) —
~/deus/.claude/wardens/qa-test-rules.md. Apply every rule whoseApplies whenmatches the changes. - The diff — run
git -C ~/deus diffandgit -C ~/deus diff --cached. If both empty, say "no changes to review" and stop. - Existing tests — find test files for the changed modules. Run
find ~/deus/src ~/deus/tests ~/deus/container -name '*.test.*' -o -name '*.spec.*' -o -name '__tests__' 2>/dev/nulland read the relevant ones. - Current state — read the changed files (not just the diff) to understand the full logic paths that need coverage.
Evaluation framework
For each changed module, evaluate:
- Happy path coverage — is the golden path (normal input → expected output) tested? Does the test assert the right thing, or just assert "no crash"?
- Edge case identification — empty input, null/undefined, boundary values, overflow, concurrent access, error states, timeout, retry exhaustion, malformed input.
- Regression risk — do the changes affect code paths that have no tests? Are callers of the modified function tested?
- Cross-platform scenarios — if the code touches filesystem paths, environment variables, child processes, or terminal behavior: are macOS, Linux, and Windows differences accounted for?
- Integration boundaries — does the change touch an external system (API, database, file system, container, MCP server)? Are those boundaries mocked AND integration-tested?
- State management — are all state transitions tested? Initial state? Cleanup/teardown? What happens if the process crashes mid-transition?
- BiDi/i18n — if the change handles text rendering, formatting, or parsing: is RTL text tested? Mixed Hebrew+English? Unicode edge cases (emoji, ZWJ sequences, surrogate pairs)?
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.
- 3d ago First seen · 67 lines · 0 tokens per session scan A 2d43befcaca6
qa-tester is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed 9d ago), licensed MIT. It adds 164 tokens to every session and 1,265 once invoked, about $0.0008 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
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
create-module
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
gtd-project-manager
Autonomous project coordination agent that tracks project status, identifies blockers and dependencies, calculates completion percentages, flags timeline risks, and suggests follow-up tasks. Proactively escalates blockers older than 7 days. Invoked by ai-task-executor for :AI:pm: tagged tasks.