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 skills add ChianW/C31 --skill c31-review-architecturegit clone --depth 1 https://github.com/ChianW/C31Wrote 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/skills/chianw/c31/c31-review-architecture)<a href="https://agentmods.dev/skills/chianw/c31/c31-review-architecture"><img src="https://agentmods.dev/badge/skills/chianw/c31/c31-review-architecture/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/skills/chianw/c31/c31-review-architecture"><img src="https://agentmods.dev/badge/skills/chianw/c31/c31-review-architecture.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.00000 | $0.00451 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
C31-review-architecture 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 10d 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
Multilingual Triggers
| Language | Trigger phrases |
|---|---|
| EN | C31-review-architecture |
| ZH | 架构审查, 架构设计 |
| JA | アーキテクチャレビュー, 設計レビュー |
Output language: Respond automatically in the user's conversation language.
C31-review-architecture
Purpose
Architecture reviewer — coupling, layering violations, abstraction leaks, scalability ceiling, tech debt trajectory.
Severity Calibration
| Level | Meaning | Fix Timeline |
|---|---|---|
| P0 | Critical — new circular dependency, monolith leak into service boundary, scalability blocked | Block merge |
| P1 | High — wrong layer for logic (business in DB, infra in domain), tight coupling introduced | Fix in PR |
| P2 | Medium — abstraction not pulling weight, premature generalization, interface bloat | Fix this sprint |
| P3 | Low — naming inconsistency, package structure could be cleaner | Backlog |
Review Checklist
- Coupling — Does this create new import cycles? Service A now depends on Service B internals?
- Layering — Domain logic leaking into controllers? Infra concerns in business rules?
- Abstraction Leaks — ORM details escaping repository? HTTP status codes in domain?
- Scalability — Stateful where stateless works? Shared mutable state? Horizontal scaling blocked?
- Boundaries — Module/package boundaries respected? Domain events vs direct calls?
- Tech Debt — Copy-paste pattern that should be abstracted? Previous hack now entrenched?
- Extensibility — New feature requires touching how many files? Open/closed principle?
- Dependencies — New library justified? Version conflict risk? License compatible?
Output Format
For each issue: P[0-3] | <concern> | <one-line summary> | <file:line>
Last line: ARCHITECTURE_SCORE: [0-10] — 10 = clean boundaries, 0 = systemic coupling introduced.
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.
- 10d ago First seen · 41 lines · 0 tokens per session scan A 6a309d3e141b
C31-review-architecture is a skill published in the GitHub repository ChianW/C31 (1 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 451 tokens. 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 skills, from other repositories
agent-code-review-swarm
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm.
agent-swarm-pr
Agent skill for swarm-pr - invoke with $agent-swarm-pr.
agent-reviewer
Agent skill for reviewer - invoke with $agent-reviewer.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agent-pr-manager
Agent skill for pr-manager - invoke with $agent-pr-manager.
agent-analyze-code-quality
Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality.