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 itlackey/akm --skill architecture-cleanupgit clone --depth 1 https://github.com/itlackey/akmWrote 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/itlackey/akm/architecture-cleanup)<a href="https://agentmods.dev/skills/itlackey/akm/architecture-cleanup"><img src="https://agentmods.dev/badge/skills/itlackey/akm/architecture-cleanup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01000 |
| Opus 5 | $0.00019 | $0.00500 |
| Sonnet 5 | $0.00008 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
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 8d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Cleanup
Use this skill for narrow architectural cleanup where the code structure should improve but the product behavior must remain exactly the same.
Core rules
- No user-visible functionality changes.
- All existing tests must continue to pass with the same validation expectations.
- The only allowed test edits are import-path or symbol-import updates caused by file or module moves.
- Do not rewrite assertions, fixtures, or expected outputs to make a refactor easier.
- Prefer adapters first, rewrites second.
- Stop if the work starts to resemble framework-building instead of targeted cleanup.
Non-goals
This work is not for:
- building a generalized plugin framework
- adding complexity for its own sake
- introducing runtime plugin loading or dynamic discovery
- replacing simple direct code with abstract dispatch where no hotspot exists
- changing command behavior, output envelopes, scoring semantics, or feature scope under the banner of refactoring
Repeated patterns
Use these patterns only when they remove a concrete maintenance problem.
Fixed-stage pipeline
Good for:
- search
- improve
- indexing
Rule:
- keep orchestration centralized
- make stage order explicit
- do not create contributor graphs
Ordered contributor registry
Good for:
- ranking signals
- proposal validators
- search-hit enrichers
Rule:
- define composition semantics once
- keep registration static and deterministic
Structural contract
Good for:
- refs
- paths
- canonical naming
Rule:
- keep it small, boring, and stable
Classification as facts
Rule:
- classification should produce facts
- downstream processes should decide how to use those facts
- avoid coupling classification directly to presentation names
SOLID / DRY / YAGNI guidance
SOLID
- Single Responsibility: move one kind of policy behind one seam
- Open/Closed: add behavior by registering a small contributor, not by growing a switchboard
- Interface Segregation: prefer several narrow contracts over one large object
- Dependency Inversion: higher-level workflows depend on small seams, not on concrete launchers or parsers
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.
- 8d ago First seen · 172 lines · 39 tokens per session scan A d1d92c29c9bc
architecture-cleanup is a skill published in the GitHub repository itlackey/akm (58 stars, last pushed 3d ago), licensed MPL-2.0. It adds 39 tokens to every session and 1,000 once invoked, about $0.0002 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-30.
Other skills, from other repositories
clean-code-dotnet
Clean Code principles adapted for C#/.NET including naming, variables, functions, SOLID, error handling, and async patterns. Use when: (1) reviewing C# code, (2) refactoring for clarity, (3) writing new code, (4) code review feedback.
Code Simplifier
Rewrites code to its simplest possible form while preserving exact external behavior (KISS, YAGNI).
scope-appropriate-architecture
Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.
refactor-agent
Use when restructure code to improve readability, maintainability, extensibility without changing external behavior.
se-dev-plugin
Plugin development for Space Engineers version 1. Search plugin code from PluginHub (client) and MagnetarHub (server) for examples and patterns.
se-dev-script
In-game (programmable block, aka PB) script development for Space Engineers version 1. Search script code for examples and patterns.