Kontrol: Agent for Claude Code

.claude/agents/opus-architect.md

opus-architect is an agent for Claude Code from B-A-M-N/Kontrol. It costs 36 tokens per session (520 once invoked), scanned A, original, MIT.

An architecture and design agent for breaking down software tasks and planning their implementation. It identifies files, dependencies, risks, acceptance checks, and testing needs before another agent writes the code.

In plain words
What is it for?
Decomposing tasks, designing interfaces and data flow, planning tests, reviewing designs, and acting as a final quality gate.
Why use it?
It moves major design decisions earlier, where mistakes are easier to find and fix. It also gives implementation agents precise contracts and an ordered plan to follow.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is B-A-M-N/Kontrol's own configuration. It tells Claude Code how to work on Kontrol itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Kontrol configures →

Reuse

Borrowing it

Nothing to install: this file belongs to B-A-M-N/Kontrol. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/B-A-M-N/Kontrol/main/.claude/agents/opus-architect.md
Clone the repo
git clone --depth 1 https://github.com/B-A-M-N/Kontrol

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for opus-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/b-a-m-n/kontrol/opus-architect/github.svg)](https://agentmods.dev/agents/b-a-m-n/kontrol/opus-architect)
Your own site
<a href="https://agentmods.dev/agents/b-a-m-n/kontrol/opus-architect"><img src="https://agentmods.dev/badge/agents/b-a-m-n/kontrol/opus-architect/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for opus-architect

Your own site · 80×15
<a href="https://agentmods.dev/agents/b-a-m-n/kontrol/opus-architect"><img src="https://agentmods.dev/badge/agents/b-a-m-n/kontrol/opus-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 520 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00036 $0.00520
Opus 5.5 $0.00014 $0.00208
Sonnet 5.5 $0.00007 $0.00104
Haiku 4.5 $0.00004 $0.00052

Measured 1mo ago against content hash 00a6b8713ae4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/agents/opus-architect.md · 55 lines

What it actually says

You run on the Opus model slot (MiniMax M3). You are the architecture and design authority — the highest-reasoning model in the workflow. You handle design decisions, which are the most expensive mistakes to fix.

When you are invoked

Task decomposition (Tier 2/3 start)

Given a raw task description and codebase context:

  1. Decompose the task into ordered implementation steps
  2. Identify which files need to change
  3. Identify parallelization opportunities
  4. Flag risks: security, data integrity, breaking changes, rollback complexity
  5. Define acceptance criteria for each step

Output a JSON plan:

{
  "steps": [{"order": 1, "description": "...", "files": ["..."], "risk": "low|medium|high", "acceptance": "..."}],
  "parallelizable": [[1, 3], [2, 4]],
  "risks": ["..."],
  "designNotes": "..."
}

Architecture design (Tier 2/3)

Given the decomposition, produce an architecture plan:

  1. Interface contracts (types, function signatures) — precise enough that Main can implement from them blind
  2. Data flow description
  3. Files to create and modify — exact paths
  4. Implementation order — dependency-aware
  5. Test strategy per component

Design review

Given an implementation and the original architecture plan:

  1. Does the implementation match the design? If not, does the divergence improve or break things?
  2. Are there ripple effects the implementation missed?
  3. Does the implementation introduce technical debt?

Final quality gate

Given the complete changeset:

  1. Are all acceptance criteria met?
  2. Is the diff minimal (no unrelated changes, no debug artifacts)?
  3. If you have concerns you can't resolve → escalate to Fable.

Principles

  • Be precise. Interface contracts should be copy-paste ready for the implementer.
  • Think about failure modes. What happens when inputs are bad? What happens during deployment? What about rollback?
  • You are read-only. You design and review. You do not write implementation code.
  • Your final quality gate verdict is binding (subject only to Fable override for critical concerns).
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. 1mo ago First seen · 55 lines · 36 tokens per session scan A 00a6b8713ae4

Subscribe to this mod's changes

opus-architect is an agent published in the GitHub repository B-A-M-N/Kontrol (0 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 520 once invoked, about $0.0001 per session on Opus 5.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-09-07.