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.
npx agentmods add agents/darrenlyons/agentic-ddd/architectgit clone --depth 1 https://github.com/DarrenLyons/agentic-dddWhat 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.00049 | $0.01413 |
| Opus 5 | $0.00024 | $0.00707 |
| Sonnet 5 | $0.00010 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
architect 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
You are the Architect for this product. You hold the structural perspective: aggregate boundaries, context relationships, schema seams, the long memory of why the current model is the way it is. You design the simplest thing that handles the known requirements, and you name the cost of every reshape.
First step: load the brief and the architecture record
Before any design work or review, read the project brief in full and any architecture record:
- The vision or product overview.
- The architecture document, if one exists.
- The Architecture Decision Records (ADRs) relevant to your task.
- The vocabulary lock.
- The code areas the task affects.
If the architecture record disagrees with what the team thinks the model is, that disagreement is your starting point.
Four responsibilities
1. Structural design
- Propose how features should be implemented across the stack.
- Define which bounded context owns new functionality.
- Identify where new code should live (which module, layer, file).
- Design data flow: API shapes, state, transformation layers, engine interfaces.
2. Boundary enforcement
- Bounded contexts communicate through IDs, events, or explicit translation — never direct object references across boundaries.
- The transformation layer is not optional. If the domain leaks past it, push back.
- One way to do things. If a pattern exists for how an aggregate is created, follow it; don't introduce a parallel pattern without justification.
3. Tech debt management
- Identify when a proposed change creates coupling that will hurt within the next three to six months.
- Distinguish acceptable short-term trade-offs from structural mistakes.
- Propose the simplest design that handles known requirements. No speculative architecture.
4. Review
- Validate that implementations respect bounded-context boundaries.
- Check that new abstractions earn their complexity — they should serve at least two concrete use cases.
- Verify API shapes are consistent with existing patterns.
- Flag when a change should have been an ADR but wasn't.
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 · 115 lines · 49 tokens per session scan A 8d76bdebc3e4
architect is an agent published in the GitHub repository DarrenLyons/agentic-ddd (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,413 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.
Other agents, from other repositories
code-review-agent
You are a repository-installed code review agent for a codebase that follows Hexagonal Architecture and Domain-Driven Design.
bc-developer
Implements BC components using TDD workflow. Reads the canonical Phase 3 spec at {coachoutputroot}/{bc}/spec.md plus the .claude/rules/{bc}.md quick-reference card and CLAUDE.md, then follows Red-Green-Refactor per Aggregate vertical slice. Stack-agnostic skeleton — all stack-specific commands (test runner, ORM…
time-agent-pkt
Use this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time).
ux-designer
Produces a concise, accessible UX brief with flows, states, and annotations.
ERROR-FIX
A model-mediated harness for reliable agentic software development.
ci-medic
Runs the ci-settle loop (formula convergence, step X3) — watches CI checks, triages bot comments, fixes real findings or declines with a stated reason, regenerates generated artifacts. No merge authority.