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/jacoby6000/smithplates/plan-architecture-refactornpx skills add Jacoby6000/Smithplates --skill plan-architecture-refactorgit clone --depth 1 https://github.com/Jacoby6000/SmithplatesWrote 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/jacoby6000/smithplates/plan-architecture-refactor)<a href="https://agentmods.dev/skills/jacoby6000/smithplates/plan-architecture-refactor"><img src="https://agentmods.dev/badge/skills/jacoby6000/smithplates/plan-architecture-refactor.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.01203 |
| Opus 5 | $0.00036 | $0.00602 |
| Sonnet 5 | $0.00014 | $0.00241 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
plan-architecture-refactor 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Architecture Refactor
Diff a current Conceptual Architecture Document (CAD) against a target
CAD and produce an ordered, incremental refactoring plan. Read the shared schema
at .ai-doc-reference/cad-contract.md (repo root) so you can align the two documents by their
stable identifiers.
The plan must be incremental and behavior-preserving: each step should leave the codebase compiling and tests green. No big-bang rewrites.
Inputs required (do not guess)
- Current CAD (
Kind: current) — produce viaanalyze-codebase-architectureif missing. - Target CAD (
Kind: target) — produce viadesign-target-architectureif missing.
If either is absent, offer to generate it with the sibling skill before
planning. If the two CADs use different Target language(s) or are otherwise
incomparable, stop and ask the user. Never fabricate the missing side.
Workflow
Copy this checklist and track progress:
- [ ] 1. Validate both CADs (kinds, comparability)
- [ ] 2. Gap analysis: align by identifier; classify each delta
- [ ] 3. Sequence deltas into safe, incremental steps
- [ ] 4. Choose a strategy per step (seams, adapters, migration)
- [ ] 5. Define validation and rollback per step
- [ ] 6. Emit the refactoring plan; offer to save
1. Validate inputs
Confirm one CAD is current and one is target, and that they are comparable.
Surface mismatches before proceeding.
2. Gap analysis
Align entries by their stable identifiers and classify every delta:
- Domain model: types to add / change / remove; invariant changes.
- Interfaces: added / removed / renamed / signature-changed.
- Implementations: to add, replace, or retire; rewiring of dependencies (e.g. container/global → explicit injection).
- Relationships: dependency-direction corrections, decoupling, layer moves.
- Patterns: patterns to introduce or remove.
Present this as a concise gap table before the step plan.
3. Sequence into incremental steps
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 · 139 lines · 71 tokens per session scan A 05111c195066
plan-architecture-refactor is a skill published in the GitHub repository Jacoby6000/Smithplates (2 stars, last pushed 23d ago), licensed MIT. It adds 71 tokens to every session and 1,203 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.
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…