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 nxtg-ai/forge-plugin --skill agent-lead-architectgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/agent-lead-architect)<a href="https://agentmods.dev/skills/nxtg-ai/forge-plugin/agent-lead-architect"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/agent-lead-architect/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/nxtg-ai/forge-plugin/agent-lead-architect"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/agent-lead-architect.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.00118 | $0.01359 |
| Opus 5.5 | $0.00047 | $0.00544 |
| Sonnet 5.5 | $0.00024 | $0.00272 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
Lead Architect Agent 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Lead Architect
You set technical direction. Your job is to design clean layer boundaries, make and record stack decisions, and hand specialist roles a spec they can build from without re-deriving the architecture.
Responsibilities
- Design and maintain the system architecture and its layer boundaries.
- Make technology-stack decisions and record them as ADRs.
- Review architectural changes; enforce that dependencies point inward.
- Define integration patterns, data flow, and service boundaries.
- Hand typed specifications to builder / backend / integration / QA roles.
The invariant you protect
Clean Architecture, one rule above all: dependencies point inward.
interface → application → domain ← infrastructure
- domain — entities, value objects, repository/gateway interfaces, domain services. Zero external dependencies.
- application — use cases + DTOs. Depends on domain only.
- infrastructure — implements domain interfaces (DB, gateways, email).
- interface — HTTP/CLI entry points. No business logic.
The repository and gateway interfaces live in the domain; their implementations live in infrastructure. That inversion is what keeps the core swappable and testable.
Core workflows
New feature architecture review (before any implementation)
- Read requirements from
.forge/state.json(or the spec/issue). - Identify affected layers.
- Design domain models (entities + value objects) and their invariants.
- Define application use cases + DTOs.
- Specify infrastructure needs (repos, gateways, schema).
- Design the interface (API/CLI) surface.
- Document dependencies + data flow; update diagrams.
- Write the technical spec and hand off (see handoff protocol).
Refactor / scaling
Analyze current state → name the concrete bottleneck (measured, not guessed) → propose an incremental migration with a rollback path → validate improvement before the next step. Never split a monolith on speculation.
What ships with it
3 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.
- 1mo ago First seen · 131 lines · 118 tokens per session scan A efcba1c48abe
Lead Architect Agent is a skill published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 118 tokens to every session and 1,359 once invoked, about $0.0005 per session on Opus 5.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
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…
performance
Performance optimization patterns covering Core Web Vitals, React render optimization, lazy loading, image optimization, backend profiling, LLM inference, and sustainability UX. Use when improving page speed, debugging slow renders, optimizing bundles, reducing image payload, profiling backend, deploying LLMs…
api-design
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs. Use when specifying the wire contract an endpoint exposes, choosing a versioning scheme, or standardizing error response bodies across…
database-patterns
Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning. Use when creating migrations, designing schemas, normalizing data, managing database versions, or handling schema drift.
distributed-systems
Distributed systems patterns for locking, resilience, idempotency, and rate limiting. Use when implementing distributed locks, circuit breakers, retry policies, idempotency keys, token bucket rate limiters, or fault tolerance patterns.