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 mickeyyaya/refactoring-skills --skill dependency-injection-module-patternsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-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/mickeyyaya/refactoring-skills/dependency-injection-module-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/dependency-injection-module-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/dependency-injection-module-patterns.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.1 | $0.00060 | $0.02428 |
| Opus 5 | $0.00030 | $0.01214 |
| Sonnet 5 | $0.00012 | $0.00486 |
| Haiku 4.5 | $0.00006 | $0.00243 |
Grade A, and why
dependency-injection-module-patterns 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Injection and Module Patterns
Overview
Dependency Injection (DI) supplies an object's dependencies from outside rather than letting it create them. Combined with the Dependency Inversion Principle (DIP), it is the primary technique for loose coupling. Module/package organisation either enables or defeats DI by controlling dependency direction.
Cross-reference: DIP — review-solid-clean-code; Factory patterns in Composition Root — design-patterns-creational-structural
When to Use
- Business logic creates its own collaborators (
new ConcreteClass()inside services) - Hidden dependencies make unit testing impossible without real infrastructure
- Evaluating framework wiring (Spring, tsyringe, FastAPI, Wire) for correctness and scope
- Reviewing module boundaries for circular imports or over-coupled packages
Quick Reference
| Pattern | Core Problem Solved | Key Red Flag |
|---|---|---|
| Constructor Injection | Mandatory deps declared up front | new ConcreteClass() inside business logic |
| Property Injection | Optional or framework-set deps | Always-required dep set via property |
| Method Injection | Per-call dependency variation | Method signature grows with each new dep |
| Interface Injection | Dependency via injector interface | Overcomplicates simple injection needs |
| Service Locator | Centralised dependency registry | Locator.get() scattered through business logic |
| DI Container / IoC | Framework manages full dep graph | container.resolve() deep in business logic |
| Composition Root | Single assembly point for object graph | Wiring logic leaking into domain layer |
| Module Organisation | Package boundaries enforce coupling | Circular imports, barrel file blowout |
DI Patterns
1. Constructor Injection
All required dependencies as constructor parameters. The default and preferred form.
Use when dependency is mandatory. Skip when circular deps make construction impossible (fix the design) or framework requires no-arg constructor.
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 · 315 lines · 60 tokens per session scan A 6d6d821ecb78
dependency-injection-module-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 2,428 once invoked, about $0.0003 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…