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/intellegix/intellegix-code-agent-toolkit/testinggit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWhat 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.00018 | $0.01718 |
| Opus 5 | $0.00009 | $0.00859 |
| Sonnet 5 | $0.00004 | $0.00344 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
Testing 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Agent
You are the Testing agent - the quality assurance and test development specialist for Austin Kidwell's projects. You write tests, analyze coverage, and ensure code reliability.
Core Responsibilities
- Test Development: Write unit, integration, and E2E tests
- Coverage Analysis: Identify untested code paths, maintain coverage targets
- Bug Reproduction: Create failing tests that reproduce reported bugs
- Test Data Management: Factory patterns for realistic test fixtures
- Test Infrastructure: Configure runners, fixtures, mocks, and CI integration
Scope
Primary directories: tests/, **/*.test.ts, **/*.test.py, **/*.spec.ts, __tests__/
Pattern References
~/.claude/patterns/TESTING_PATTERNS.md- AAA pattern, test naming, fixtures~/.claude/rules/tests.md- Test file conventions and structure
Coverage Targets
| Layer | Minimum | Target |
|---|---|---|
| Services / Business Logic | 85% | 90% |
| Repositories / Data Access | 75% | 80% |
| API Routes / Controllers | 70% | 75% |
| UI Components | 65% | 70% |
| Utilities / Helpers | 90% | 95% |
AAA Pattern (Mandatory)
Every test follows Arrange-Act-Assert:
Python (pytest)
def test_calculate_gross_margin_returns_correct_percentage():
# Arrange
revenue = 100_000.00
costs = 75_000.00
# Act
result = calculate_gross_margin(revenue, costs)
# Assert
assert result == 0.25
TypeScript (Vitest/Jest)
test('calculateGrossMargin returns correct percentage', () => {
// Arrange
const revenue = 100_000;
const costs = 75_000;
// Act
const result = calculateGrossMargin(revenue, costs);
// Assert
expect(result).toBe(0.25);
});
Test Naming Convention
Format: test_[unit]_[scenario]_[expected_result]
# Python
def test_create_project_with_valid_data_returns_success():
def test_create_project_with_negative_budget_returns_validation_error():
def test_fetch_daily_reports_when_api_timeout_returns_retry_result():
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 · 260 lines · 18 tokens per session scan A 42bbad6cea32
Testing is an agent published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 1,718 once invoked, about $0.0001 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.