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 agentmods add skills/firstp1ck/pi-coding-agent-forge/architecture-reviewnpx skills add Firstp1ck/pi-coding-agent-forge --skill architecture-reviewgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/firstp1ck/pi-coding-agent-forge/architecture-review)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/architecture-review"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/architecture-review.svg" alt="Measured on agentmods" 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.00043 | $0.01346 |
| Opus 5 | $0.00022 | $0.00673 |
| Sonnet 5 | $0.00009 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
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 6d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review
Structured architecture review for the user's projects. Evaluates module boundaries, dependency graphs, coupling/cohesion, and adherence to design principles.
Quick Start
Run a Quick Architecture Check
For a single module or component:
- Map the structure: What modules/components exist? How are they organized?
- Trace dependencies: Who depends on whom? Are there cycles?
- Assess coupling: How tightly are modules connected? Can you change one without breaking others?
- Evaluate cohesion: Does each module have a single, clear responsibility?
- Recommend: Prioritized findings with rationale
Architecture Review Checklist
Module Boundaries
- Each module has a clear, single responsibility
- Public APIs are minimal — expose only what's needed
- Internal implementation details are hidden (encapsulation)
- Module names accurately describe their responsibility
- No "God module" that does everything
Dependency Analysis
- Dependencies flow in one direction (no cycles)
- High-level modules don't depend on low-level implementation details
- External dependencies are isolated behind abstractions
- Dependency count per module is reasonable (< 7 direct deps as guideline)
Coupling Assessment
| Coupling Type | Description | Severity |
|---|---|---|
| Content coupling | Module directly accesses internals of another | Critical |
| Common coupling | Modules share global mutable state | High |
| Control coupling | Module controls flow of another via flags | Medium |
| Stamp coupling | Modules share complex data structures | Low-Medium |
| Data coupling | Modules share only necessary data | Acceptable |
| Message coupling | Modules communicate via messages/events | Best |
Cohesion Assessment
| Cohesion Type | Description | Quality |
|---|---|---|
| Coincidental | Elements grouped arbitrarily | Poor |
| Logical | Elements grouped by category, not function | Poor |
| Temporal | Elements grouped by when they execute | Fair |
| Procedural | Elements grouped by execution order | Fair |
| Communicational | Elements operate on same data | Good |
| Sequential | Output of one is input of next | Good |
| Functional | All elements contribute to a single task | Best |
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.
- 6d ago First seen · 181 lines · 43 tokens per session scan A 8c80803a6956
architecture-review is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (77 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,346 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
Avant-Garde Frontend Architect
Expert frontend design and UI implementation with a focus on bespoke, visually striking, and minimalist interfaces. Trigger with 'ULTRATHINK' prefix for deep architectural analysis. Automatically detects and uses existing UI libraries (Shadcn UI, Radix, MUI) while applying unique styling. Includes a personalized…
council
Run a 5-adviser council to stress-test any decision. Five distinct lenses (Contrarian, First-Principles, Expansionist, Outsider, Executor) answer independently, then anonymously peer-review each other, and a Chairman synthesizes a single clear recommendation. Kills sycophancy and groupthink on high-stakes calls.
Beads Workflow Optimizer
Optimizes Beads workflow activation, parallel processing, and task management. Use when working with Beads issues, managing dependencies, or optimizing development workflows in projects with complex task dependencies.
ae-proof-agent
Diligence-grade product and technical analysis for the ae.ltd proof-agent concept, including comparison against Cursor and Omnara, MVP and production architecture, red-team review, and build-vs-buy evaluation. Use when Codex needs to create or critique PRDs, tech specs, competitive diligence, leadership memos, or…
npm-docs
Use this skill whenever the user asks about npm, package management, publishing packages, semantic versioning, npm CLI commands, or Node.js dependencies. Covers npm 12.x including the registry, scopes, organizations, security (audit, provenance, 2FA), CI/CD integration, workspaces, scripts, .npmrc configuration, and…
dependency-manager
Manage project dependencies — update packages, audit vulnerabilities, resolve conflicts, and keep dependencies healthy. Use when updating packages, fixing vulnerability alerts, or resolving dependency issues.