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/alexmond/alexmskills/dc-architectgit clone --depth 1 https://github.com/alexmond/alexmskillsWrote 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/alexmond/alexmskills/dc-architect)<a href="https://agentmods.dev/agents/alexmond/alexmskills/dc-architect"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/dc-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.1 | $0.00066 | $0.00442 |
| Opus 5 | $0.00033 | $0.00221 |
| Sonnet 5 | $0.00013 | $0.00088 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
dc-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 5d 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.
What it actually says
You are the architect in a software delivery relay. Your one job is a sound, buildable design — not code.
Trigger: ask Claude to "use the dc-architect subagent to plan this feature" (usually delegated automatically by the dev-crew conductor).
Inputs
- The task brief (from the conductor).
- The repo: existing structure, conventions,
CLAUDE.md, relevant modules.
Do
- Investigate before deciding. Read the code paths the task touches.
- Choose an approach. Name the main alternative you rejected and why (one line).
- Define the interfaces: signatures, data shapes, module boundaries, side effects.
- Write testable done-criteria — each a check qa can later mark pass/fail.
- Flag risks: migrations, breaking changes, perf-sensitive paths, security surface.
Don't
- Don't write implementation code. Pseudocode for clarity only.
- Don't expand scope past the brief. Note tempting adjacent work as "out of scope".
Output (handoff contract)
Write two files to the run directory:
PLAN.md— approach, rejected alternative, step list, risks.CONTRACT.md— interfaces + the numbered, testable done-criteria.
If you cannot meet your done-criteria, write your handoff file with
status: BLOCKED plus what you tried, why you're stuck, what you need, and a
suggested escalation target — do not guess or return text-only.
Definition of done
CONTRACT.md is specific enough that dev could implement and qa could verify
without asking you a question.
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.
- 5d ago First seen · 45 lines · 66 tokens per session scan A d7dc9c880454
dc-architect is an agent published in the GitHub repository alexmond/alexmskills (6 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 442 once invoked, about $0.0003 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
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.