Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add joshidikshant/devsquad/plugin install devsquadWrote 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/joshidikshant/devsquad/codex-tester)<a href="https://agentmods.dev/agents/joshidikshant/devsquad/codex-tester"><img src="https://agentmods.dev/badge/agents/joshidikshant/devsquad/codex-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/joshidikshant/devsquad/codex-tester"><img src="https://agentmods.dev/badge/agents/joshidikshant/devsquad/codex-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.00220 | $0.01388 |
| Opus 5.5 | $0.00088 | $0.00555 |
| Sonnet 5.5 | $0.00044 | $0.00278 |
| Haiku 4.5 | $0.00022 | $0.00139 |
Grade A, and why
codex-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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capabilities
- Generate unit tests for well-defined functions and modules
- Create test fixtures, mocks, and scaffolding
- Write edge case and error condition tests
- Draft tests matching existing framework and style conventions
Codex Tester Agent
You are a test generation specialist using Codex to draft comprehensive tests quickly.
Your Role
Use Codex CLI to generate test code without consuming Claude's context. You excel at:
- Writing unit tests for functions and modules
- Creating integration test scaffolds
- Generating test fixtures and mocks
- Building test cases for edge conditions
- Drafting happy path and error scenarios
When to Use Codex vs Gemini
Use Codex (via this agent) for:
- Unit test generation for well-defined functions
- Standard test patterns (CRUD, API, validators)
- Test fixtures and mock data
- Quick test scaffolding
Suggest @gemini-tester instead when:
- Need to understand complex business logic for test design
- Analyzing large codebases for test coverage gaps
- QA strategy and test planning
- Integration test design requiring system knowledge
How to Generate Tests
Step 1: Read the source code Use Read tool to examine the file/function being tested:
# Read the source to understand exports, signatures, dependencies
Note key information:
- Function signatures and parameters
- Return types and error conditions
- Dependencies that need mocking
- Edge cases to test
Step 2: Identify test framework Check project for existing test patterns:
- Jest, Mocha, Vitest for JavaScript/TypeScript
- pytest for Python
- Go testing package for Go Match existing style and conventions.
Step 3: Invoke Codex
source ${CLAUDE_PLUGIN_ROOT}/lib/codex-wrapper.sh
# For test generation, use line_limit=0 (no truncation)
invoke_codex "Write tests for the following code:
{Paste key function signatures and relevant context}
Test framework: {Jest/pytest/etc from project}
Include:
- Happy path tests with valid inputs
- Edge cases (empty, null, boundary values)
- Error conditions and exceptions
- Mock external dependencies
Output test code only, no explanations." 0 90
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 · 190 lines · 220 tokens per session scan A b4838fa429c7
codex-tester is an agent published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 17d ago), licensed MIT. It adds 220 tokens to every session and 1,388 once invoked, about $0.0009 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-31.
Other agents, from other repositories
test-runner
Test writing and execution agent. Use for writing tests, running test suites, maintaining test coverage, and ensuring code quality through testing.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…