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 srstomp/pokayokay --skill architecture-reviewgit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/architecture-review)<a href="https://agentmods.dev/skills/srstomp/pokayokay/architecture-review"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/architecture-review/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/srstomp/pokayokay/architecture-review"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/architecture-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00041 | $0.00462 |
| Opus 5 | $0.00020 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
architecture-review 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
Architecture Review
Analyze, audit, and improve project structure.
Key Principles
- Measure before changing — Map structure and identify concrete issues before proposing changes
- Clear boundaries — Layers (UI, logic, data) separated with consistent dependency direction
- Colocation — Related code together; easy to find, change, and delete features
- Incremental migration — Refactor in phases, validate each step with tests
Quick Assessment
- No circular dependencies
- Consistent directory naming and grouping (by feature or by type)
- Single responsibility per file/module, reasonable file sizes (<500 lines)
- External dependencies isolated, shared code properly extracted
- New developers can navigate and find code for any feature easily
Quick Start Checklist
- Map current structure: directory tree, dependency graph, module boundaries
- Identify issues: circular deps, god modules, leaky abstractions, deep nesting
- Classify severity: critical (blocks dev), high (maintenance burden), medium/low (friction)
- Propose target structure with migration plan
- Execute incrementally, validating with tests after each move
References
| Reference | Description |
|---|---|
| analysis-techniques.md | Dependency graphs, complexity metrics, code analysis |
| refactoring-patterns.md | Safe refactoring techniques, migration strategies |
| structural-patterns.md | Directory structures for different project types |
| dependency-management.md | Circular deps, coupling, module boundaries |
| cleanup-strategies.md | Dead code removal, consolidation, naming conventions |
| anti-rationalization.md | Iron Law, common rationalizations, red flag STOP list for architecture discipline |
What ships with it
6 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.
- 10d ago First seen · 44 lines · 41 tokens per session scan A c56d3dbe919e
architecture-review is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 462 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.