developer-agent

A software-development agent that turns architecture and work-unit specifications into code. It can also scan an existing codebase and produce structured analysis for the architecture agent.

In plain words
What is it for?
It helps reverse-engineer projects, generate code from specifications, run build and package-manager commands, and execute tests.
Why use it?
It reduces the manual effort of implementing detailed designs and examining an unfamiliar codebase before making changes.

Agent

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/amadeus-dlc/amadeus/developer-agent
Clone the repo
git clone --depth 1 https://github.com/amadeus-dlc/amadeus
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 628 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00628
Opus 5 $0.00000 $0.00314
Sonnet 5 $0.00000 $0.00126
Haiku 4.5 $0.00000 $0.00063

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

Security

Grade A, and why

developer-agent 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 2d 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.

docs/guide/agents/developer-agent.md · 46 lines

How it starts

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

Developer Agent

Languages: English | 日本語

Agent deep dive · User GuideAgentsdeep dives · Technical reference: developer-agent

The amadeus-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the amadeus-architect-agent synthesizes.

The amadeus-developer-agent leads two stages across Inception and Construction. One of its stages (Code Generation) runs as a subagent — an autonomous subprocess that operates without user interaction. It has Bash access for running build tools, package managers, and test commands.

Workspace Detection (0.2) runs deterministically inside amadeus-utility init as a rule-based scanner. The amadeus-developer-agent is not involved in Initialization.

Stages Led

Stage Phase Description
2.1 Reverse Engineering (code scan) Inception Deep code scan producing structured analysis for architect synthesis
3.5 Code Generation Construction Implements units of work from design specifications (per unit)

Stages Supported

Stage Phase Contribution
2.2 Practices Discovery Inception Code-pattern evidence scan
3.1 Functional Design Construction API contracts and data model input
4.3 Deployment Execution Operation Database migrations

What to Expect

During Code Generation, the amadeus-developer-agent runs as a subagent — you will not interact with it directly. You see a progress indicator and then the results when it completes. The orchestrator first presents a code generation plan for your approval, then the subagent implements each step.

Application code is written directly to the workspace root (not into the intent's record dir). The code-summary.md artifact in the intent's record dir documents what was created or modified.

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

  1. 2d ago First seen · 46 lines · 0 tokens per session scan A e9d3babf7ecf

Subscribe to this mod's changes

developer-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 628 tokens. 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.