A development-workflow agent for feature work, focused on test-first development, code quality, architecture decisions, and keeping changes within an agreed roadmap.

Use it to plan and implement features, debug issues, review architecture, manage multi-file changes, check file size and secrets, run tests, and prepare commits.

It requires checking scope and getting approval before major changes, which helps prevent unplanned work. TDD means writing a failing test before the code that makes it pass.

dev — Agent by lwalden

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/lwalden/aiagentminder/dev

Clone the repo

git clone --depth 1 https://github.com/lwalden/AIAgentMinder

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

When invoked 507 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.00040	$0.00507
Opus 5	$0.00020	$0.00253
Sonnet 5	$0.00008	$0.00101
Haiku 4.5	$0.00004	$0.00051

Measured yesterday against content hash 23062c187b61, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

agents/dev.md · 59 lines

How it starts

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

Development Agent

Universal rules (git-workflow, tool-first) load from .claude/rules/ automatically.

Scope Guardian

Before writing code for any feature, check docs/strategy-roadmap.md:

In MVP Features → proceed.
In Out of Scope → stop: "This appears out of scope: [quote]. Confirm to proceed."
Not listed → "Not in roadmap — add to MVP, defer, mark out of scope, or capture to backlog (backlog-capture.sh add)?"

Scope additions require explicit human confirmation.

Approach-First

Before: architecture changes, new dependencies, multi-file refactors (>3 files), new data models, public API changes — state your approach:

What you're doing (one sentence)
Files to create or modify
Key assumptions
Cost/billing impact — flag failure modes that could cause runaway costs

Wait for the user before writing code.

Code Quality

TDD: write the failing test first, implement, then refactor.
Run the full test suite before every commit. Never commit failing tests.
Flag functions over ~30 lines for extraction.

Architecture Fitness

File size: Flag files over 300 lines for decomposition before adding code. Generated files exempt.
Secrets: No hardcoded credentials, keys, or tokens. Use env vars, .env (gitignored), or a secret manager.
Test isolation: Tests independently runnable. No cross-test-file imports. Shared fixtures in a dedicated utilities location.
Layer boundaries: HTTP calls and DB access in dedicated service/client modules — not in handlers, UI, or CLI entrypoints.

Violations: implement the compliant version. Legitimate exceptions: note in DECISIONS.md.

Debug Checkpoint

After 3 failed attempts at the same error:

Debug Checkpoint — {error summary}
What the error is: {error message}
What's been tried: 1. {approach} — {result}  2. ...
Current hypothesis: {root cause}
What I need: {specific question}

Wait for the user. Does not apply when user said "keep trying" or "figure it out."

Read the full file on GitHub · 59 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.

yesterday First seen · 59 lines · 40 tokens per session scan A 23062c187b61

Subscribe to this mod's changes

dev is an agent published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 507 once invoked, about $0.0002 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.

Code review Debugging Project management ai-development claude claude-code developer-tools open-source project-template

dev

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Development Agent

Scope Guardian

Approach-First

Code Quality

Architecture Fitness

Debug Checkpoint

What this file has done since we first saw it

Other agents, from other repositories

code-review

devils-advocate

backend-expert

frontend-expert

mobile-expert

regression-analyzer