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 Emasoft/ai-maestro-architect-agent --skill amaa-modularizationgit clone --depth 1 https://github.com/Emasoft/ai-maestro-architect-agentWrote 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/emasoft/ai-maestro-architect-agent/amaa-modularization)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-modularization"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-modularization/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/emasoft/ai-maestro-architect-agent/amaa-modularization"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-modularization.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.00035 | $0.00724 |
| Opus 5 | $0.00017 | $0.00362 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
amaa-modularization 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modularization Skill
Overview
Guides decomposition into modules with clear boundaries, minimal coupling, and high cohesion. Covers SOLID principles, boundary identification, API design, dependency management, and modularization validation.
Prerequisites
- Project source code available for analysis
Instructions
Use when starting new projects, refactoring monoliths, analyzing coupling, designing inter-module APIs, or planning microservices migration.
- Apply Principles - Apply SOLID to guide decomposition
- Identify Boundaries - Find natural module boundaries via domain mapping
- Design APIs - Define interfaces and contracts between modules
- Manage Dependencies - Graph dependencies, resolve circulars, extract shared code
- Validate - Verify testability, coupling metrics, deployment independence
See Detailed Procedures for the full phase checklist.
Checklist
Copy this checklist and track your progress:
- Apply SOLID principles to guide decomposition
- Identify natural module boundaries via domain mapping
- Design interfaces and contracts between modules
- Graph dependencies and resolve circulars
- Extract shared code into dedicated modules
- Validate testability, coupling metrics, and deployment independence
Reference Documents
| Document | Contents |
|---|---|
| SOLID Principles | Overview, The Five SOLID Principles, Applying SOLID to Module Boundaries, Validation Checklist, Common Violations and Fixes, Summary |
| Boundary Patterns | Overview, Core Principle, Step 1: Map Domain Concepts, Step 2: Identify Change Vectors, Step 3: Find Natural Seams, Step 4: Define Bounded Contexts, Step 5: Validate Boundaries |
| API Design Guide | Overview, Core API Design Principles, API Contract Templates, Versioning Strategy, Compatibility Rules, Data Transfer Objects (DTOs), Error Handling Contracts |
| Detailed Procedures | What is a Module?, Why Modularization Matters, Detailed Phase Checklist, Examples, Troubleshooting, Next Steps |
What ships with it
14 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.
- README.md 1.7 KB
- references/api-design-guide.md 16 KB
- references/boundary-patterns.md 11 KB
- references/dependency-analysis.md 13 KB
- references/detailed-procedures.md 6.0 KB
- references/module-testing.md 19 KB
- references/op-apply-solid-principles.md 8.6 KB
- references/op-decompose-monolith.md 12 KB
- references/op-design-module-apis.md 9.5 KB
- references/op-detect-circular-dependencies.md 8.9 KB
- references/op-identify-module-boundaries.md 9.9 KB
- references/op-manage-module-dependencies.md 11 KB
- references/solid-principles.md 8.8 KB
- references/strangler-pattern.md 16 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.
- 8d ago First seen · 80 lines · 35 tokens per session scan A 0c8524b9f3f1
amaa-modularization is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 10d ago), licensed MIT. It adds 35 tokens to every session and 724 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…