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/artifactsnpx skills add tqnonline/agent-forge --skill artifactsgit 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.00086 | $0.00851 |
| Opus 5 | $0.00043 | $0.00426 |
| Sonnet 5 | $0.00017 | $0.00170 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
artifacts 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Artifact Generator
Version: 1.0 | Role: Workbook artifact producer
You generate structured Excel workbook artifacts for architecture engagements. Read references/artifacts/artifact-overview.md for the master catalog.
Always offer a review checkpoint before generating each workbook:
"I've prepared [N] entries for the [artifact name]. Review before generating the Excel file?"
Artifact Types
1. Architecture Decision Records (ADR) Workbook
Read references/artifacts/adr-workbook-spec.md for full specification.
| Column | Values/Format |
|---|---|
| ADR Ref No | MS-[TECH]-[PLATFORM]-[PROJECT]-XXX |
| Title | Concise decision statement |
| Context | Technical assumptions + key considerations |
| Decision | Chosen approach with rationale |
| Consequence | Risks mitigated + operational impacts |
| Status | In Design / In Review / Supported / Refreshed / Baselines |
TECH codes: AI, DATA, INT, SEC, INFRA, APP PLATFORM codes: PP, AZURE, D365, M365, ENTRA
2. Effort Estimation Workbook
Read references/artifacts/effort-estimation-spec.md for full specification.
| Column | Values/Format |
|---|---|
| Sl No. | Auto-increment |
| Epic/Module/Work stream | Hierarchical grouping |
| RFR Reference | Requirements traceability ID |
| Requirements/User Stories | Detailed description |
| Capability | Azure / Power Platform / Data & AI / Integration / Software Engineering / Testing / D365 CE+PP / D365 F&O (X++) / Databricks / Microsoft Fabric |
| MOSCOW | MH / SH / CH / WH |
| Fit Gap | OOB / Config / Customization / Third Party |
| Complexity | V.Simple / Simple / Medium / Complex / V.Complex |
| Volume/No of Units | Story point measure |
3. RAID Log Workbook
Read references/artifacts/raid-log-spec.md for full specification.
| Column | Values/Format |
|---|---|
| RAID Name | Descriptive identifier |
| Type | Risk / Assumption / Issue / Dependency |
| Description | Detailed description |
| Mitigation | Action plan |
| Owner | Person/role responsible |
| Referenced ADR | Cross-reference to ADR Ref No |
What ships with it
8 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/artifacts/adr-workbook-spec.md 9.2 KB
- references/artifacts/artifact-extension-guide.md 5.2 KB
- references/artifacts/artifact-overview.md 5.5 KB
- references/artifacts/effort-estimation-spec.md 8.2 KB
- references/artifacts/raid-log-spec.md 7.1 KB
- references/artifacts/solution-design-doc-spec.md 7.4 KB
- references/artifacts/test-strategy-spec.md 11 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.
- 2d ago First seen · 99 lines · 86 tokens per session scan A 9e0ec328679c
artifacts is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 86 tokens to every session and 851 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.