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/aiforging/aiforging/architecture-analyzernpx skills add aiforging/aiforging --skill architecture-analyzergit clone --depth 1 https://github.com/aiforging/aiforgingWhat 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.00068 | $0.02444 |
| Opus 5 | $0.00034 | $0.01222 |
| Sonnet 5 | $0.00014 | $0.00489 |
| Haiku 4.5 | $0.00007 | $0.00244 |
Grade A, and why
architecture-analyzer 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 3d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Analyzer
Purpose
Read a target project's current shape and compare it against the AI Forging architectural ideals documented in ${CLAUDE_PLUGIN_ROOT}/conventions/architecture/ and ${CLAUDE_PLUGIN_ROOT}/conventions/tdd/. Produce a clear, honest report the user can act on.
This skill is read-only. It never creates, edits, deletes, or moves files in the target project. If a user asks the skill to "fix" what it found, refer them to /aiforging:execute-plan (which is deferred for v0.1.0) or to manual refactoring with the pattern library.
When to activate
- Invoked explicitly by
/aiforging:setupStep 5 against each confirmed backend or fullstack project. - Invoked directly by a user who wants a standalone audit without re-running setup.
Inputs
- Target project root: absolute path to the project to analyze. Required.
- Detected ProjectInfo: the JSON blob from
scripts/detect-project.py, if already available. If not, the skill runs the detector first.
Outputs
Write the report to <target>/.aiforging/ANALYSIS.md. Also return a concise top-line summary (score + top 3 findings) to the caller for inline display.
The report has this shape:
# AI Forging Architecture Analysis
**Project:** <name>
**Path:** <abs path>
**Stack:** <detected stack, e.g., symfony-php + doctrine + phpunit>
**Analyzed:** <ISO date>
**Score:** <0-10>
## Summary
<2-3 sentences on the overall shape. What's healthy, what's not.>
## Findings
<One section per finding, ordered by severity (critical → high → medium → low → info).>
### [<severity>] <Finding title>
**What we saw:**
<Concrete evidence with file paths and line numbers or quoted snippets.>
**Why it matters:**
<One paragraph referencing the relevant AI Forging convention doc.>
**How to fix it:**
<High-level refactor direction. Do NOT write patch/code.>
**Related conventions:**
- `conventions/architecture/<relevant-doc>.md`
- `conventions/refactoring/anti-patterns/<relevant>.md`
## Checklist
<Yes/No table of the capability contract items, see below.>
## Next
The proposed plan for remediation will be written to
`<target>/.aiforging/PROPOSED_PLAN.md` by `/aiforging:setup` Step 6.
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.
- 3d ago First seen · 192 lines · 68 tokens per session scan A e56bd8ec0278
architecture-analyzer is a skill published in the GitHub repository aiforging/aiforging (4 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 2,444 once invoked, about $0.0003 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…