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 mrinalwadhwa/fluent --skill review-architecturegit clone --depth 1 https://github.com/mrinalwadhwa/fluentWrote 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/mrinalwadhwa/fluent/review-architecture)<a href="https://agentmods.dev/skills/mrinalwadhwa/fluent/review-architecture"><img src="https://agentmods.dev/badge/skills/mrinalwadhwa/fluent/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/mrinalwadhwa/fluent/review-architecture"><img src="https://agentmods.dev/badge/skills/mrinalwadhwa/fluent/review-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00313 |
| Opus 5 | $0.00018 | $0.00156 |
| Sonnet 5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
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 9d 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
Purpose
Decide whether the code's architecture is fit to ship. Identify improvements that would make the codebase simpler, more coherent, and easier to change.
Scope
The invoking layer decides what's in scope. For a diff-scoped review, that's the structural choices in the diff. For a full-codebase audit, that's the codebase's overall structure. Even in a diff-scoped review, evaluate the changes in the context of the entire codebase — a boundary that looks fine in isolation can be wrong in context. Check each choice for structural quality and check the codebase as a whole for coherence.
Method
-
Read the code under review to understand its structure — module boundaries, key abstractions, dependencies.
-
Read
references/architecture.mdfor architectural principles. Read any related guides it points to for the code under review. -
For each in-scope structural choice:
- Evaluate against the principles in
references/architecture.md. - Identify improvements.
- Evaluate against the principles in
-
Check for anti-patterns from
references/architecture.md. -
For each improvement, decide if it blocks shipping. Circular dependencies, god objects, and coupling that will block near-term work typically block. Small simplifications, naming preferences, and style choices typically don't.
The invoking layer may add checks in addition to those above.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 29 lines · 37 tokens per session scan A 7298b6be14aa
review-architecture is a skill published in the GitHub repository mrinalwadhwa/fluent (88 stars, last pushed 8d ago), licensed Apache-2.0. It adds 37 tokens to every session and 313 once invoked, about $0.0002 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-30.
Other skills, from other repositories
code_review
Code review — security audit, quality assessment, suggested fixes.
requesting-code-review
The formal protocol for requesting and processing peer code reviews from the Auditor sub-agent during CIEL execution.
coding-standards
Baseline cross-project engineering conventions for readability, immutability, and architecture.
everything-claude-code-conventions
Core repository standards for naming, structure, commits, and workflows.
ciel-review-and-adversarial
CIEL's adversarial review framework for rigorous code review, security auditing, and adversarial testing.
code-review
Revisão holística pré-commit (estilo PR Review). Valida o diff contra as 3 memórias vivas, a spec da task e Clean Code, com pré-condição de evidência de teste. Executada pelo Tech Lead; veredito escrito em review.md.