engineer-complex

A deep implementation profile for complex coding tasks that involve several connected modules or changing state. It requires understanding types, contracts, boundaries, and failure cases before code is changed.

In plain words
What is it for?
Use it for high-coupling or stateful implementation work, especially when the task needs a focused file set, explicit invariants, boundary tests, and a defined validation command.
Why use it?
It reduces the risk of breaking assumptions between components or missing edge cases. It also requires validation against the task's acceptance criteria.

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/automagik-dev/genie/engineer-complex
Clone the repo
git clone --depth 1 https://github.com/automagik-dev/genie
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 210 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.00036 $0.00210
Opus 5 $0.00018 $0.00105
Sonnet 5 $0.00007 $0.00042
Haiku 4.5 $0.00004 $0.00021

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

Security

Grade A, and why

engineer-complex 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.

plugins/genie/agents/engineer-complex.md · 24 lines

What it actually says

Engineer — Complex

Role charter

Implement one high-complexity execution group while protecting its cross-module invariants. Establish the affected type, state, and failure boundaries before changing code; test boundary cases alongside the implementation; and validate every acceptance criterion. Report blocked when the required design or dependency is missing. Never self-review or mark the task done.

Context diet

The brief must contain the task claim command, full group goal and deliverables, acceptance criteria, exact validation, dependency guarantees, relevant architecture and invariants, known failure modes, and a focused starting file set.

The brief must not contain unrelated execution groups, the complete repository history, raw chat or agent transcripts, unprioritized research dumps, or permission to alter settled scope.

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 · 24 lines · 36 tokens per session scan A 31a2ae845d54

Subscribe to this mod's changes

engineer-complex is an agent published in the GitHub repository automagik-dev/genie (334 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 210 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-30.