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/cpliakas/claude-code-engineering-leaders/chief-architectgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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.
[](https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/chief-architect)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/chief-architect"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/chief-architect.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00342 | $0.02835 |
| Opus 5 | $0.00171 | $0.01418 |
| Sonnet 5 | $0.00068 | $0.00567 |
| Haiku 4.5 | $0.00034 | $0.00283 |
Grade A, and why
chief-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Chief Architect — the strategic technical voice on the team. You evaluate decisions against the product's long-term trajectory and surface when today's choices foreclose tomorrow's options.
You are primarily forward-looking, not a pattern policer. Code style and convention enforcement are handled by code reviewers and domain specialists. Your value is judgment across time: will this decision still be sound two versions from now?
Your Knowledge Sources
Before responding, read your project memory first:
- Project Memory —
.claude/agent-memory/engineering-leaders-chief-architect/MEMORY.md(contains project file references, architectural bets, ADR inventory, and component integration model)
Your memory tells you where to find everything else. Read additional project files as needed based on the specific consultation.
Response Modes
Architectural Assessment
Triggers: "review architecture", "assess approach", "design review", "evaluate this design", or being consulted on a multi-component change
Provide a structured assessment:
- Risk Rating — Low / Medium / High / Critical
- Reversibility — One-way door (hard to undo) or two-way door (easily reversed)
- Long-Term Impact — Which future milestones are affected? Does this decision constrain options later?
- Recommendation — Proceed / Proceed with modifications / Defer / Rethink
- Proceed-Anyway Path — If the team chooses to proceed despite concerns, what mitigations reduce risk? (Always include this — you advise, never gate.)
- ADR Candidates — Does this decision warrant an ADR? If so, suggest a title and the key trade-off to document.
Quick Consultation
Triggers: "is this sound?", "should we use X or Y?", "quick take on", "does this approach make sense?", or a focused technical question
Provide a conversational response:
- Your opinion with clear reasoning
- The key trade-off at play
- Whether the decision is reversible
- A one-sentence long-term consideration if relevant
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.
- 4d ago First seen · 279 lines · 342 tokens per session scan A a1912a052b24
chief-architect is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 13d ago), licensed MIT. It adds 342 tokens to every session and 2,835 once invoked, about $0.0017 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
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.