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 Razaib-khan/ForgeWeave --skill architecture-designergit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/razaib-khan/forgeweave/architecture-designer)<a href="https://agentmods.dev/skills/razaib-khan/forgeweave/architecture-designer"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/architecture-designer/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/razaib-khan/forgeweave/architecture-designer"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/architecture-designer.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.00022 | $0.00596 |
| Opus 5 | $0.00011 | $0.00298 |
| Sonnet 5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
Architecture Designer 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 9d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Designer
Purpose
Design system-level architecture before any code is written. Produces module boundaries, service decomposition, data flow diagrams, and scaling strategy. Ensures the architecture is coherent, testable, and aligned with project constraints.
When to Use
- Starting a new project or major subsystem
- The current architecture cannot support upcoming requirements
- Performance, scalability, or reliability concerns need addressing at the architectural level
- Multiple services or modules need to be designed together
When Not to Use
- The change is contained within a single module — use
planner+code-builder - The user just needs a quick code pattern — not architectural design
- The architecture is already documented and just needs implementation
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
requirements |
string | Yes | Functional and non-functional requirements |
constraints |
string | No | Technical, organizational, or timeline constraints |
existing_architecture |
string | No | Description of existing system if extending it |
Expected Outputs
| Output | Description |
|---|---|
| Module decomposition | List of modules with responsibilities |
| Data flow | How data moves between modules and external systems |
| Scaling strategy | How the system handles growth |
| Technology decisions | Key tech choices with rationale |
Exact Workflow Steps
- Understand requirements and constraints thoroughly
- Identify bounded contexts and module boundaries
- Define interfaces and data flow between modules
- Design for failure: error handling, retries, fallbacks
- Plan scaling strategy (horizontal vs vertical, caching, sharding)
- Document technology decisions with alternatives considered
- Review with planner to create execution plan
Required Checks
- Every requirement is addressed by the architecture
- Module boundaries are clear and non-overlapping
- Data flow is documented with direction and format
- Failure modes are identified per module
What ships with it
2 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.
- 9d ago First seen · 85 lines · 22 tokens per session scan A a1b59e945600
Architecture Designer is a skill published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 596 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-08-31.
Other skills, from other repositories
api-design
A guide to designing web APIs—the interfaces that let software systems exchange data—using REST, gRPC, and GraphQL patterns.
latency-analysis
Analyze endpoint latency trends using historical check data from memory. Detects slow degradation, spikes vs sustained issues, and calculates baseline deviations.
response-validation
Validate API response structure and content. Detects schema drift, unexpected null values, and abnormal response sizes.
golang-manual-di
Guides manual dependency injection wiring for Go services: three-tier naming taxonomy (Provide/MustProvide/Must), Must-pattern entrypoints, OS-signal-driven context lifecycle, common provider structs, infrastructure must-builders, interface-segregated bus registration, decorator/tracing wrappers, and…
terraform-infrastructure
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.