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 strikersam/autonomous-ai-agency --skill modularity-reviewgit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/modularity-review)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/modularity-review"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/modularity-review/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/strikersam/autonomous-ai-agency/modularity-review"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/modularity-review.svg" alt="Reviewed on agentmods" width="80" 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.00091 | $0.01737 |
| Opus 5 | $0.00046 | $0.00869 |
| Sonnet 5 | $0.00018 | $0.00347 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
modularity-review 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 12d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: modularity-review
The Core Principle
Modularity is about change. A codebase is modular when it is crystal-clear which components need to change for a given requirement, and ideally that number is small — preferably one. If change radiates unpredictably, the system is coupled.
A secondary modern concern: modularity makes code accessible to AI. LLMs have finite context windows. Tightly coupled codebases force large, entangled contexts onto every reasoning task. Well-modularized code lets AI (and humans) reason about one bounded piece at a time.
When to Use
- Before designing a new module, service, or capability
- When a change requires touching 5+ files across unrelated modules
- When tests are hard to write because of dependency tangles
- When a new team member can't understand a module without reading 3 others
- When the AI agent loop requires large context to accomplish a focused task
Part A: Reviewing Existing Code for Modularity Problems
Step 1 — Map the dependency graph
For each module in the repo, list what it imports:
# Python: list all internal imports
grep -r "^from\|^import" --include="*.py" . | grep -v ".venv" | grep -v "test_"
Build a mental (or written) graph: which modules depend on which.
Step 2 — Identify coupling smells
Look for these patterns:
| Smell | Description | Example in this repo |
|---|---|---|
| Feature envy | Module A uses many internals of module B | proxy.py reaching into agent/loop.py internals |
| Shotgun surgery | One change requires edits in 5+ files | Adding a new model type requires editing registry, classifier, router, and tests |
| Divergent change | One module changes for many unrelated reasons | proxy.py handles auth, routing, streaming, rate limiting all at once |
| Improper abstraction | Implementation detail leaks through module boundary | Caller knows which HTTP client the callee uses |
| Circular dependency | A imports B, B imports A | Usually causes import errors in Python |
| God module | One file does everything | proxy.py risks becoming this |
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.
- 12d ago First seen · 211 lines · 91 tokens per session scan A 8f7f471c0301
modularity-review is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 1,737 once invoked, about $0.0005 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
codebase-sync
Convention discovery and rule generation from codebase analysis. Scans project structure, builds search indexes, identifies patterns, and generates enforceable rules.
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
code-review-orchestration
6-agent parallel code review orchestration covering architecture, security, performance, testing, quality, and documentation dimensions with weighted scoring.
code-review-pipeline
Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
plan-implementation
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.