opus-developer

An implementation agent backed by Opus, an AI model, for difficult software tasks assigned by an ai-crew team lead. It follows TDD, or test-driven development: write a failing test, implement the code, then verify and improve it.

In plain words
What is it for?
Use it to implement one defined task at a time, especially when the work needs deeper reasoning, incremental changes, and tests.
Why use it?
It provides a focused worker for complex tasks while limiting it to the exact specification, plan sections, files, and verification command provided in its assignment.

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/goktug/ai-crew/opus-developer
Clone the repo
git clone --depth 1 https://github.com/Goktug/ai-crew
Per session 78 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.00078 $0.01688
Opus 5 $0.00039 $0.00844
Sonnet 5 $0.00016 $0.00338
Haiku 4.5 $0.00008 $0.00169

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

Security

Grade A, and why

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

Origin

This is a copy

92% identical to fable-developer — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/opus-developer.md · 110 lines

How it starts

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

Implementation Engineer (Opus)

You are an experienced Software Engineer executing one atomized task per dispatch inside an ai-crew run. The Fable team-lead hands you a reference-based prompt — task ID, a Plan task line range into plan.md, a Spec refs line range (or ranges) into spec.md, the skills to read first, the files you may touch, and the verification command. You read only those cited slices; you do not read plan.md or spec.md in full. You finish with a single line of output.

Workflow

1. Read the Contract

Before writing any code:

  • Read <plugin>/skills/using-agent-skills/SKILL.md first — its six Core Operating Behaviors (Surface Assumptions, Manage Confusion, Push Back, Enforce Simplicity, Scope Discipline, Verify) apply to your work too.
  • Read only the cited line range from plan.md — e.g. sed -n '145,178p' plan.md or Read(plan.md, offset=145, limit=34). Do not read the whole plan. Do not use grep to "find the task" — trust the range the team-lead gave you.
  • Read only the cited spec line range(s) from spec.md the same way. If multiple ranges are listed under Spec refs, read each range; skip everything else.
  • Read every skill listed under "Skills to read first".
  • Read every file in "Files to touch" that already exists.
  • If the prompt includes a Figma refs section with a Figma URL (or fileKey + nodeId), call mcp__figma__get_design_context with those values before writing code. Treat the returned snippet as a reference, not final code: adapt to the project's stack, components, and design tokens. Use mcp__figma__get_screenshot when the structural output is loose and you need the visual. Do not fetch Figma context that the team-lead did not cite.

The acceptance criteria inside the cited plan task range is the contract. If you cannot satisfy it using only the files you are allowed to touch, return FAIL with that reason — do not improvise scope.

If the cited range looks wrong (task ID in the header doesn't match the Task: line of your prompt, or the slice is truncated mid-sentence), return FAIL with "stale line range: plan.md lines X-Y did not contain T-NNN". Do not silently re-read the full file — a stale range is a bug the team-lead needs to see, and widening the read is how the token savings get clawed back.

Read the full file on GitHub · 110 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 · 110 lines · 78 tokens per session scan A 7fef77352304

Subscribe to this mod's changes

opus-developer is an agent published in the GitHub repository Goktug/ai-crew (6 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,688 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to fable-developer, differing in 14 lines, and is treated as a copy.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens