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 agentmods add rules/andr-ca/agentharness/dependency-injectiongit clone --depth 1 https://github.com/andr-ca/agentharnessWhat 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 | $0.00043 | $0.00678 |
| Opus 5 | $0.00022 | $0.00339 |
| Sonnet 5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
dependency-injection 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Injection
One rule: depend on abstractions, receive them via constructor, never create them internally.
The Pattern
# BAD — hard to test, tightly coupled
class OrderService:
def __init__(self):
self.db = Database() # creates its own dependency
self.email = EmailClient() # can't inject fakes in tests
# GOOD — testable, decoupled
class OrderService:
def __init__(self, db: Database, email: EmailClient) -> None:
self.db = db
self.email = email
// BAD
class OrderService {
private db = new Database(); // hidden dependency
}
// GOOD
class OrderService {
constructor(private db: Database, private email: EmailClient) {}
}
Rules
| Do | Don't |
|---|---|
| Inject dependencies via constructor | Create dependencies with new inside a class |
| Depend on interfaces/protocols | Depend on concrete types when an abstraction exists |
| Make dependencies explicit | Use service locators (Container.get(...)) inside business logic |
| Keep constructors simple — no logic | Do work in __init__/constructors |
| Use fakes/stubs in tests | Patch global singletons in tests |
When to Use a DI Container
Use a container (FastAPI's Depends, tsyringe, Wire for Go) when:
- The object graph has 3+ levels of nesting
- You need lifetime management (singleton vs. transient vs. scoped)
- You need request-scoped dependencies (e.g., database sessions per HTTP request)
Don't use a container for:
- Small scripts or utilities (manual wiring is simpler and clearer)
- Value objects (DTOs, records) — they carry data, not behavior
- Stateless pure functions
Lifetimes
| Lifetime | When to use | Example |
|---|---|---|
| Singleton | Shared state across the app; expensive to create | DatabasePool, ConfigLoader |
| Scoped | One instance per request/unit of work | DbSession, UserContext |
| Transient | Stateless; cheap to create | EmailFormatter, Validator |
Anti-Patterns
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.
- yesterday First seen · 82 lines · 43 tokens per session scan A e286e241ba2c
dependency-injection is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 678 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 cursor rules, from other repositories
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
lemoncrow.execute
LemonCrow execute mode reference for Cursor.
prompt-routing
Route tasks to the correct Universal AI Engineering Prompt.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.