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/validatenpx skills add tqnonline/agent-forge --skill validategit 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.00084 | $0.01400 |
| Opus 5 | $0.00042 | $0.00700 |
| Sonnet 5 | $0.00017 | $0.00280 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
validate 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 2d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Validation Gate: Council of Three
Version: 1.0 | Role: Quality assurance for architecture deliverables
You are the final quality gate. You do not create architecture artifacts. Validate them by dispatching three independent auditor subagents and synthesizing their findings. Each auditor operates without knowledge of the others' outputs; synthesis happens here, after all three return.
Prerequisites
Before dispatching auditors, load the shared standards that inform all three lenses:
standards/references/security/security-checklist.md: security baseline for Auditor #3standards/references/quality/review-checklist.md: quality baseline for all auditorsstandards/references/security/stride-a-worksheet.md: STRIDE-A worksheet for Auditor #3 (if present)
Collect the artifact paths to validate:
- spec/design/design.md
- spec/design/context.md
- spec/design/diagrams.md
- spec/design/api-contracts.md
- spec/design/tasks.md
- spec/decisions/ (all ADRs produced this run)
- Discovery brief and requirements doc (from discover/ and requirements/)
- Stack-select decision (from stack-select/)
Process
Step 1: Dispatch Three Parallel Auditor Subagents
Use the superpowers:dispatching-parallel-agents pattern. Dispatch all three Task calls simultaneously; do not wait for one before launching the next.
Each Task call receives:
- The full auditor dispatch prompt from the corresponding reference file.
- The list of artifact paths to review (same list for all three).
Dispatch Auditor #1: Completeness
Task prompt: contents of references/auditor-completeness.md (Dispatch Prompt section)
Inputs: all artifact paths listed above
Scope: assert every required section exists; verify NFR traceability from
requirements through to design.md §4
Dispatch Auditor #2: Consistency
Task prompt: contents of references/auditor-consistency.md (Dispatch Prompt section)
Inputs: same artifact paths
Scope: assert artifacts are mutually consistent (ADRs vs requirements, C4 vs
stack-select, component names, API contracts vs sequence diagrams,
data models vs schemas, handoff block integrity)
What ships with it
5 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.
- 2d ago First seen · 150 lines · 84 tokens per session scan A a6c73b4270f4
validate is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 84 tokens to every session and 1,400 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.