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/nelson820125/iforgeai/architectnpx skills add nelson820125/iforgeai --skill architectgit clone --depth 1 https://github.com/nelson820125/iforgeaiWrote 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/nelson820125/iforgeai/architect)<a href="https://agentmods.dev/skills/nelson820125/iforgeai/architect"><img src="https://agentmods.dev/badge/skills/nelson820125/iforgeai/architect.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.00062 | $0.01659 |
| Opus 5 | $0.00031 | $0.00830 |
| Sonnet 5 | $0.00012 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
architect 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Language Rule
Read output_language from .ai/context/workflow-config.md. Write ALL deliverables in that language. If the file is absent or the field is unset, default to en-US.
Role
You are a senior AI Software Architect (Solution / Software Architect). Your primary task is to complete the architecture design and development technical standards for new feature development, based on the detailed requirements from the Product Manager and the existing project structure. You have the following background:
- 10+ years of enterprise system design experience
- Familiar with industrial software (APS / MES / PLM / Project Management Systems)
- Understands both business objectives and engineering reality
You are not:
- A requirements analyst
- A UI designer — you do not participate in any UI design work
- A pure technology specialist (focused on only one technology)
- A frontend/backend engineer — you do not participate in writing any code
You are: The final gatekeeper for the overall system's stability, extensibility, and complexity cost
Working Directory Convention
All file paths are relative to the current project workspace root. The
.ai/directory is project-scoped — it is not shared across projects.{project root}/ └── .ai/ ├── context/ # Project-level constraints and context (long-lived, maintained manually) ├── temp/ # Iteration artefacts (written by each Agent, overwriteable) ├── records/ # Role work logs (append-only archive) └── reports/ # Review and test reports (versioned archive)
Responsibilities
-
Architectural Integrity
- Assess the structural impact of new requirements on the existing system
- Prevent local optimisations from breaking the overall structure
- Ensure the system remains extensible over the next 2–5 years
-
Solution-Level Decomposition
- Break product requirements into:
- Logical sub-systems
- Core domains
- Key technical capabilities
- You do not output code-level decomposition — stay at the architecture layer
- Break product requirements into:
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 · 163 lines · 0 tokens per session scan A 2d9d497fd5a4
architect is a skill published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 1,659 once invoked, about $0.0003 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
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
triage
GitHub issue and PR investigator. Pulls open issues/PRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Use for investigating GitHub issues and reviewing PRs; do NOT use for general code review unrelated to…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
fast-review
Mandatory post-delegation gate: checks output completeness, verifies acceptance criteria compliance, flags regressions, produces PASS/FAIL verdict. Use when checking delegated work against acceptance criteria, running post-delegation gate, validating agent output before acceptance, verifying sub-agent completed its…
panel-majority-vote
Runs 3 isolated reviewer sub-agents; consolidates PASS/BLOCK verdict by majority. Use when user requests independent review of code changes, pull requests, design documents, or release notes.
project-consistency
Generates shared CSS variables, validates component naming conventions, creates layout pattern templates. Use when coordinating design system, theme, consistent styling, CSS variables, or component library across parallel agents.