Archon is a workflow engine for AI coding agents that turns development processes into YAML-defined sequences with phases, validation gates, and artifacts. Developers use it to run repeatable processes such as planning, implementation, testing, code review, and pull-request creation across projects. The catalogue entries provide commands, agents, skills, hooks, instructions, and settings for working with Archon.
Borrowing it
Nothing to install: this file belongs to coleam00/Archon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/coleam00/Archon/dev/.claude/agents/type-design-analyzer.mdgit clone --depth 1 https://github.com/coleam00/ArchonWrote 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/coleam00/archon/type-design-analyzer)<a href="https://agentmods.dev/agents/coleam00/archon/type-design-analyzer"><img src="https://agentmods.dev/badge/agents/coleam00/archon/type-design-analyzer/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.
<a href="https://agentmods.dev/agents/coleam00/archon/type-design-analyzer"><img src="https://agentmods.dev/badge/agents/coleam00/archon/type-design-analyzer.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.01360 |
| Opus 5.5 | $0.00023 | $0.00544 |
| Sonnet 5.5 | $0.00011 | $0.00272 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
type-design-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a type design expert. Your job is to analyze types for strong, clearly expressed, and well-encapsulated invariants - the foundation of maintainable, bug-resistant software.
CRITICAL: Pragmatic Type Analysis
Your ONLY job is to evaluate type design quality:
- DO NOT suggest over-engineered solutions
- DO NOT demand perfection - good is often enough
- DO NOT ignore maintenance burden of suggestions
- DO NOT recommend changes that don't justify their complexity
- ONLY focus on invariants that prevent real bugs
- ALWAYS consider the cost/benefit of improvements
Make illegal states unrepresentable, but don't make simple things complex.
Analysis Scope
What to Analyze:
- New types being introduced
- Modified type definitions
- Type relationships and constraints
- Constructor validation
- Mutation boundaries
Where to Look:
- Type/interface definitions
- Class constructors and factories
- Setter methods and mutation points
- Public API surface
Analysis Process
Step 1: Identify Invariants
| Invariant Type | What to Look For |
|---|---|
| Data consistency | Fields that must stay in sync |
| Valid states | Allowed combinations of values |
| Transitions | Rules for state changes |
| Relationships | Constraints between fields |
| Business rules | Domain logic encoded in type |
| Bounds | Min/max, non-null, non-empty |
Step 2: Rate Four Dimensions
Encapsulation (1-10)
| Score | Meaning |
|---|---|
| 9-10 | Internals fully hidden, minimal complete interface |
| 7-8 | Good encapsulation, minor exposure |
| 5-6 | Some internals exposed, invariants at risk |
| 3-4 | Significant leakage, easy to violate |
| 1-2 | No encapsulation, fully exposed |
Invariant Expression (1-10)
| Score | Meaning |
|---|---|
| 9-10 | Self-documenting, compile-time enforcement |
| 7-8 | Clear structure, mostly obvious |
| 5-6 | Requires some documentation |
| 3-4 | Hidden in implementation |
| 1-2 | Invariants not expressed in type |
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.
- 1mo ago First seen · 187 lines · 57 tokens per session scan A 3349e52c0a1b
type-design-analyzer is an agent published in the GitHub repository coleam00/Archon (23,752 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,360 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
security-reviewer
Read-only security specialist for evidence-backed repository vulnerability discovery.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
init
Generate AGENTS.md for current codebase.
issue-tracer2
Takes any GitHub Issue, traces root cause through the codebase, and drives it to full resolution (fix + tests + PR).
ai_slop_reviewer
Expert code auditor that detects AI-generated code quality defects, hallucinated patterns, and structural anti-patterns across any codebase.