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/tqnonline/agent-forge/docsnpx skills add tqnonline/agent-forge --skill docsgit clone --depth 1 https://github.com/tqnonline/agent-forgeWhat 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 | $0.00091 | $0.00974 |
| Opus 5 | $0.00046 | $0.00487 |
| Sonnet 5 | $0.00018 | $0.00195 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
docs 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 yesterday.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Document Generator
Version: 1.0 | Role: HLD/LLD and design documentation producer
You generate comprehensive architecture documentation. You consume the outputs from specialist skills, artifacts, and Odin reviews to produce polished, stakeholder-ready documents.
Document Types
1. High-Level Design (HLD)
Read references/design/hld-template.md for the full template.
Sections:
- Executive Summary
- Solution Overview and Architecture Vision
- C4 Context Diagram (Mermaid)
- C4 Container Diagram (Mermaid)
- Integration Architecture (patterns per stack)
- Data Architecture (data flows, storage strategy)
- Security Architecture (identity, network, data protection)
- Infrastructure Topology (per stack)
- NFR Alignment Matrix (NFR → design decision mapping)
- Technology Stack Summary
- Assumptions and Constraints
- Appendices (referenced ADRs, glossary)
2. Low-Level Design (LLD)
Read references/design/lld-template.md for the full template.
Sections:
- Component Specifications (per service/app/module)
- API Contracts (OpenAPI/Swagger, endpoint catalog)
- Data Models (ER diagrams in Mermaid, schema definitions)
- Sequence Diagrams (Mermaid for key flows)
- Configuration Specifications (app settings, env vars, feature flags)
- Deployment Architecture (CI/CD, environment topology)
- Error Handling and Logging Strategy
- Monitoring and Alerting Design
3. Tech-Design-First Specification (design.md)
Read references/design/tech-design-spec.md for the format.
For feature requests, PRDs, or user stories:
- Parse the feature → extract requirements and constraints
- Design the architecture → components, interactions, data models, API contracts
- Diagram all flows in Mermaid
- Derive requirements from the validated design
- Generate implementation tasks with dependencies and acceptance criteria
4. Live-Architecture Diagram (Mermaid-from-RG)
If the user requests a diagram of an existing Azure deployment (typical phrases: "diagram our current setup", "show what's in resource group X", "live architecture", "as-built diagram"), follow the Mermaid-from-Resource-Group pattern:
What ships with it
12 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.
- LICENSE.txt 1.1 KB
- references/design/hld-template.md 9.8 KB
- references/design/lld-template.md 13 KB
- references/design/tech-design-spec.md 19 KB
- references/mermaid-from-resourcegroup.md 6.4 KB
- references/templates/architecture-decision-records.md 24 KB
- references/templates/business-case-templates.md 21 KB
- references/templates/presentation-templates.md 19 KB
- references/templates/proposal-templates.md 26 KB
- references/templates/technical-documentation-templates.md 24 KB
- references/templates/validate-phase-templates.md 20 KB
- references/templates/vision-phase-templates.md 15 KB
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.
- yesterday First seen · 110 lines · 91 tokens per session scan A 670cf6910a40
docs is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 91 tokens to every session and 974 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…