Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/event4u-app/agent-confignpx agentmods add skills/event4u-app/agent-config/architecture-review-lensWrote 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/event4u-app/agent-config/architecture-review-lens)<a href="https://agentmods.dev/skills/event4u-app/agent-config/architecture-review-lens"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/architecture-review-lens/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/event4u-app/agent-config/architecture-review-lens"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/architecture-review-lens.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.00036 | $0.01193 |
| Opus 5 | $0.00018 | $0.00596 |
| Sonnet 5 | $0.00007 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
architecture-review-lens 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 11d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
architecture-review-lens
Fifth judge in the
/review-changesfamily. Reviews a diff for architectural fit, not correctness, security, tests, or style. Catches what the other four miss: layer violations, wrong dependency direction, leaking abstractions, and broken cross-service contracts. Sibling ofjudge-bug-hunteret al. — never overlaps.
When to use
/review-changesdispatches its "architecture" slice to this skill.- A reviewer asks "does this belong here?", "should this be in the domain layer?", or "is this leaking storage details?".
- A diff adds a cross-service call, event, or contract.
Do NOT use when:
- The diff is documentation-only or a formatting-only change.
- The concern is correctness — route to
judge-bug-hunter. - The concern is security — route to
judge-security-auditor. - The concern is naming or DRY — route to
judge-code-quality. - The concern is whether to make the architectural change — route
to
decision-recordfirst.
Procedure
1. Anchor on the system shape
Read the codebase's stated architecture (ADRs, AGENTS.md, module docs). If no shape is documented, infer it from folder structure and surface the gap. You are judging the diff against the stated shape, not a fantasy ideal.
2. Inspect each changed file for fit
For every changed file, answer:
| Question | Smell when "no" |
|---|---|
| Does this file live in the right layer? | Layer violation |
| Are imports flowing in the allowed direction? | Inverted dependency |
| Does this leak a storage / framework detail? | Leaky abstraction |
| Is the public API of the module still the same? | Contract drift |
| Does a cross-service call respect its contract? | Contract break |
Each smell is a finding with a file:line citation.
3. Check the seams
Pay special attention to:
What ships with it
1 file 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.
- 11d ago First seen · 142 lines · 36 tokens per session scan A 0b6fb12c1704
architecture-review-lens is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,193 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-31.
Other skills, from other repositories
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
pr-blocker-summarizer
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.
receiving-code-review
Processes review feedback until the change is approved.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
session-start
Load handoff on session start, review lessons, output readiness signal. Triggers: '/session-start', 'start session'. Skip if: first session (no handoff), user requests 'start fresh', or standalone question unrelated to project context.
status
Display current progress of Draft tracks and active tasks. Shows phases, completion percentages, and blocked items.