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 vikisingh23/neuraforge-ai --skill architecture-reviewgit clone --depth 1 https://github.com/vikisingh23/neuraforge-aiWrote 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/vikisingh23/neuraforge-ai/architecture-review)<a href="https://agentmods.dev/skills/vikisingh23/neuraforge-ai/architecture-review"><img src="https://agentmods.dev/badge/skills/vikisingh23/neuraforge-ai/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/vikisingh23/neuraforge-ai/architecture-review"><img src="https://agentmods.dev/badge/skills/vikisingh23/neuraforge-ai/architecture-review.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.00015 | $0.00114 |
| Opus 5 | $0.00008 | $0.00057 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00011 |
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 8d 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
Review code architecture and design patterns.
What it checks
- Layer separation (controller → service → repository)
- Dependency injection usage
- Module boundaries (no cross-boundary DB access)
- Single responsibility (line limits, god class detection)
- Composition over inheritance
For full instructions, read agents/architecture-review.md.
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.
- 8d ago First seen · 21 lines · 15 tokens per session scan A d5d9a201c48c
architecture-review is a skill published in the GitHub repository vikisingh23/neuraforge-ai (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 114 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
api-audit
API and endpoint integrity audit across 10 dimensions (D1-D10) plus optional contract stability (D11) and optional OWASP API Security Top 10 (D12: BOLA/BOPLA/BFLA, mass assignment, JWT alg-confusion, GraphQL introspection). Covers validation, payloads, pagination, errors, caching, HTTP semantics, waterfalls, rate…
performance-audit
Full-stack performance health check across 12 dimensions. Rendering, bundles, assets, API/network, algorithms, memory, database, caching, Web Vitals, backend runtime, concurrency, and framework-specific pathologies. Evidence-based Impact Models with confidence tiers and a prioritized optimization roadmap. Switches…
craft-backend
The Craftsman standard for building and reviewing backend code — API routes, request validation, the authentication boundary, service/business logic, error handling, route rate-limit middleware, third-party integrations, and background jobs. Use this WHENEVER the work touches the server side: adding or reviewing a…
audit
Use before releases, after large PRs, or during onboarding to run a single read-only analysis of a codebase's quality, risk, and design. The one analysis front door. Reads the glossary to resolve a selector that zooms across three layers — track, aspect, family/category/entity — then delegates to the oop-orchestrator…
pattern-implement
Use after /audit pattern-fit surfaces an opportunity, or directly on a design-pattern id, to implement that pattern into a target scope with a safe parallel-change sequence and verify it with the project's own detected commands. Resolves the pattern against the glossary and delegates to the oop-orchestrator in…
improve
Use after /audit flags problem areas, or directly on a smell/antipattern/family, to apply the smallest corrective refactor and verify it with the project's own detected commands. The FIX action reached from the audit report's Recommended Actions handoff (/fix-risks ). Resolves the selection against the glossary and…