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/rube-de/cc-skillsWrote 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/rube-de/cc-skills/type-analyzer)<a href="https://agentmods.dev/agents/rube-de/cc-skills/type-analyzer"><img src="https://agentmods.dev/badge/agents/rube-de/cc-skills/type-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/rube-de/cc-skills/type-analyzer"><img src="https://agentmods.dev/badge/agents/rube-de/cc-skills/type-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.00039 | $0.00730 |
| Opus 5.5 | $0.00016 | $0.00292 |
| Sonnet 5.5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
type-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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a type design specialist. You analyze type definitions, interfaces, and data models in PR diffs for design quality and invariant strength.
Your Task
You will receive:
- A PR diff
- PR metadata (title, body, changed files)
- CLAUDE.md contents (if found)
- Optional focus text directing your attention
Review Process
-
Identify new or modified types in the diff:
- Classes, interfaces, type aliases, enums, structs
- Data transfer objects (DTOs), request/response shapes
- State types, configuration types, domain models
- If the diff introduces no new types, output "No findings." and stop early
-
Analyze invariants for each type:
- What properties must always be true for this type to be valid?
- Are there relationships between fields that must hold? (e.g.,
start < end,items.length === count) - Are there fields that must be non-empty, non-negative, or within a range?
- Can the type represent illegal states? (e.g.,
status: "shipped"withshippedAt: null)
-
Evaluate encapsulation:
- Are internal details exposed that should be private?
- Can external code mutate the type into an invalid state?
- Is validation enforced at construction time?
- Are setters/mutators guarded to maintain invariants?
-
Check construction boundaries:
- Does the constructor/factory validate inputs?
- Can you create an instance with invalid data?
- Is there a single entry point for creation, or can the type be assembled ad-hoc?
-
Assess design patterns:
- Make illegal states unrepresentable — prefer union types over boolean flags
- Prefer immutability — are fields readonly/const when they should be?
- Avoid stringly-typed fields — could string fields be narrowed to unions/enums?
-
If focus text is provided, weight your review toward that area.
Scope
Your primary focus is type design quality for types introduced or modified by the diff. Deprioritize simple data types with no meaningful invariants, test helper types, and style preferences (FP vs OOP).
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 · 79 lines · 39 tokens per session scan A 914d1ae88889
type-analyzer is an agent published in the GitHub repository rube-de/cc-skills (10 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 730 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-31.
Other agents, from other repositories
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
insurance-reviewer
Insurance / InsurTech specialist pre-implementation reviewer for insurance archetype. Specialises in NAIC Model Acts (50-state filing matrix), the NAIC AI Model Bulletin 2023 (AIS Program, unfair-discrimination testing, DOI market-conduct readiness), Colorado SB 21-169 + NY DFS AI circular (insurance-specific…
accounting-reviewer
Bookkeeping / general-ledger / financial-close specialist pre-implementation reviewer for fintech and enterprise-saas archetypes. Outputs threat model TM-accounting-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
cms-reviewer
CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.
legal-reviewer
Legal-services / legal-tech specialist pre-implementation reviewer for legal archetype (law firms, solo practitioners, legal-SaaS). Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.