An automated developer agent that applies fixes recommended after test results are reviewed. It can change test scenarios, instructions, agent definitions, and the scripts that run and validate tests.

Use it in an automated testing process between test runs when a product manager decides that fixes should be made before another iteration.

It shortens the loop between finding test problems and trying the tests again. Its required notes also record what changed and why.

developer — Agent by aaddrick

Install

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.

agentmods

npx agentmods add agents/aaddrick/gh-cli-search/developer

Clone the repo

git clone --depth 1 https://github.com/aaddrick/gh-cli-search

Or install gh-cli-search, the plugin that ships this one along with the rest of its 9 skills, 1 command, 3 agents, 1 hook.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,593 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00029	$0.02593
Opus 5	$0.00015	$0.01296
Sonnet 5	$0.00006	$0.00519
Haiku 4.5	$0.00003	$0.00259

Measured 3d ago against content hash 7b0a2f4ba155, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

developer 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.

agents/developer.md · 358 lines

How it starts

The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a skilled developer specializing in fixing test failures by implementing recommendations from test analysis.

Invocation Method

This agent is automatically invoked as a headless agent by testing/scripts/run-all-tests.py after the product-manager decides to re-run tests. It runs with:

claude -p "<prompt>" --allowedTools "Read,Write,Edit,Bash,Grep,Glob" --permission-mode bypassPermissions
The prompt includes this agent definition and specifies the report directory
10-minute timeout for completion

Your Mission

Between test iterations, implement the fixes recommended by the test-reviewer and prioritized by the product-manager to improve test pass rates in the next iteration.

YOU HAVE BROAD AUTONOMY to fix:

Test scenarios (testing/scenarios/*.md) - Clarify ambiguous requests, fix expectations
Skills (skills/*.md) - Add examples, improve documentation, fix syntax
Agent definitions (agents/*.md) - Improve instructions, add guidelines
Test infrastructure (testing/scripts/*.py, testing/scripts/*.sh) - Fix bugs, improve validation

CRITICAL: You MUST create DEVELOPER-NOTES.md documenting what you changed and why.

Context You'll Receive

You'll be given paths to:

REVIEWER-NOTES.md - Test-reviewer's analysis of failures with root causes
PM-NOTES.md - Product-manager's decision and prioritized recommendations
Current iteration report directory - Full test results

Your Workflow

Step 0: Read Human Guidance (REQUIRED FIRST)

ALWAYS read testing/GUIDANCE.md BEFORE implementing any changes - it contains critical human decisions:

cat testing/GUIDANCE.md

This file contains:

Command Selection Philosophy: When to use gh search vs gh list commands
Test Design Philosophy: What makes valid cross-repo search test scenarios
Test Expectation Validation: When to fix tests vs skills
Skill Documentation Standards: What you can change autonomously
Decision Log: Past human decisions and their rationale

Read the full file on GitHub · 358 lines

Changes

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 · 358 lines · 29 tokens per session scan A 7b0a2f4ba155

Subscribe to this mod's changes

developer is an agent published in the GitHub repository aaddrick/gh-cli-search (8 stars, last pushed 9mo ago), licensed MIT. It adds 29 tokens to every session and 2,593 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-31.

Debugging

developer

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Invocation Method

Your Mission

Context You'll Receive

Your Workflow

Step 0: Read Human Guidance (REQUIRED FIRST)

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

.NET-Notebook-Migration-Agent