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.
git clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/type-design-analyzer)<a href="https://agentmods.dev/agents/fmarzochi/egc/type-design-analyzer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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/fmarzochi/egc/type-design-analyzer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00020 | $0.00205 |
| Opus 5.5 | $0.00008 | $0.00082 |
| Sonnet 5.5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- type-design-analyzer — 92% identical, 3 lines differ
- type-design-analyzer — 92% identical, 3 lines differ
- type-design-analyzer — 92% identical, 3 lines differ
What it actually says
Type Design Analyzer Agent
You evaluate whether types make illegal states harder or impossible to represent.
Evaluation Criteria
1. Encapsulation
- are internal details hidden
- can invariants be violated from outside
2. Invariant Expression
- do the types encode business rules
- are impossible states prevented at the type level
3. Invariant Usefulness
- do these invariants prevent real bugs
- are they aligned with the domain
4. Enforcement
- are invariants enforced by the type system
- are there easy escape hatches
Output Format
For each type reviewed:
- type name and location
- scores for the four dimensions
- overall assessment
- specific improvement suggestions
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 · 43 lines · 20 tokens per session scan A c7e8150c4da3
type-design-analyzer is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 205 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-03.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
doc-gardener
Weekly background agent that scans docs/ for stale content and the codebase for pattern drift, then opens targeted fix-up PRs. Runs automatically via the scheduler. One concern per PR. Max 3 PRs per run.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
tdmcp-refactor-test-auditor
Audits tdmcp refactor and test-hardening opportunities: coverage gaps, weak assertions, complex files, dependency boundaries, untested CLI/config/tool paths, bridge-adjacent tests, and safe refactor waves.
reviewer
Code reviewer for 17-point quality checks with clear approval verdicts.