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 skills add MartinPLarsen/claude-architecture-skills --skill architecture-cleanupgit clone --depth 1 https://github.com/MartinPLarsen/claude-architecture-skillsWrote 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/martinplarsen/claude-architecture-skills/architecture-cleanup)<a href="https://agentmods.dev/skills/martinplarsen/claude-architecture-skills/architecture-cleanup"><img src="https://agentmods.dev/badge/skills/martinplarsen/claude-architecture-skills/architecture-cleanup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/martinplarsen/claude-architecture-skills/architecture-cleanup"><img src="https://agentmods.dev/badge/skills/martinplarsen/claude-architecture-skills/architecture-cleanup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00134 | $0.01994 |
| Opus 5.5 | $0.00054 | $0.00798 |
| Sonnet 5.5 | $0.00027 | $0.00399 |
| Haiku 4.5 | $0.00013 | $0.00199 |
Grade A, and why
architecture-cleanup 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Cleanup
Analyse an architecture-map (map.js) to find what can be safely removed, prove each
candidate statically, and paint the findings back onto the map as a red removable overlay.
Core principle — advisor by default. Step 1 only reads code and annotates the map. It NEVER edits source. Removal happens only in Step 2, after the user's explicit approval, as a branch + PR. No runtime telemetry exists, so claims are "no static references found" — never "unused in production".
When to use
- "Clean up / debloat the architecture", "find dead code", "what can I delete".
- After mapping a repo and wanting to shrink it before adding features.
- Not for line-level perf or refactor proposals — that's
architecture-improve. - Recommended order: cleanup → improve (don't optimise code you're about to delete).
Input — map.js (ADR-010)
The input is <repo>/architecture-map/map.js (window.MAP_DATA). If it doesn't exist, build
it first with the architecture-map skill, then run cleanup on the result. Node file-refs
(path:line) and the status field are what cleanup cross-checks against the live code.
Step 1 — advisory pass (default)
- Ensure the map exists & is fresh. No
map.js→ build viaarchitecture-map. A stale map gives stale findings, so re-map if the repo moved since it was generated. - Git-snapshot the map FIRST (ADR-011). Before annotating, make sure
map.jsis committed (orgit stash-clean), so backout is onegit restore. The overlay is additive — original node data is only augmented, never overwritten — but the snapshot is the undo guarantee. - Topology layer (deterministic). Run the helper to get the per-node worklist — inbound/
outbound edge counts,
isolatedflag,inboundFrom, blast-radius, the proposed-node list, and duplicate-tech groups:node <SKILL_DIR>/analyze-map.mjs <repo>/architecture-map/map.js > /tmp/worklist.json - Static cross-check (judgment). For each candidate, grep its
path:linerefs in the real code and assign a confidence tier (table below). The helper gives topology; grep gives the code half. Dynamic/string-based calls grep can't follow → 🟡, never 🔴. - Bucket into the 7-category taxonomy. Every finding =
category + tier + evidence (path:line + ref-count) + blastRadius. Build afindings.jsonarray (one object per node or edge — see helper--selftestfor the shape). ⚫️ guesses are NOT surfaced. - Write the overlay (additive). Flag the map's nodes/edges
removablewithout touching their data:
If the repo's viewer predates the overlay, refresh it so the red toggle appears:node <SKILL_DIR>/apply-overlay.mjs <repo>/architecture-map/map.js /tmp/findings.json > /tmp/map.js \ && mv /tmp/map.js <repo>/architecture-map/map.jscp <ARCH_MAP_SKILL_DIR>/assets/index.html <repo>/architecture-map/. - Report — plain-language finding cards. Hand the user one plain-language card per finding
(format:
references/finding-card-and-issues.md— What it is / Why / What you gain / Risk, with the technical evidence folded at the bottom). Grouped by category, then tier. Plus the open command:open <repo>/architecture-map/index.htmlshows a 🔴 Removable toggle (on by default); clicking a node shows tier + evidence + blast-radius.
What ships with it
3 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.
- 2mo ago First seen · 130 lines · 134 tokens per session scan A 4084a5a5c568
architecture-cleanup is a skill published in the GitHub repository MartinPLarsen/claude-architecture-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 134 tokens to every session and 1,994 once invoked, about $0.0005 per session on Opus 5.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 debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…