dependency-injection

A set of TypeScript patterns for dependency injection, a way to provide a class with the services it needs instead of creating them itself. It covers constructor and property injection and circular dependencies.

In plain words
What is it for?
Use it when structuring TypeScript applications with services such as user accounts, email notifications, and logging.
Why use it?
It makes service relationships easier to manage and test, while addressing cases where services depend on each other in a loop.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/jahands/prompts/dependency-injection
Clone the repo
git clone --depth 1 https://github.com/jahands/prompts
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,421 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01421
Opus 5 $0.00006 $0.00711
Sonnet 5 $0.00003 $0.00284
Haiku 4.5 $0.00001 $0.00142

Measured 3d ago against content hash ce055fe05d77, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

cursor-rules/test-rules/dependency-injection.mdc · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Guidelines for implementing dependency injection patterns, choosing between constructor and property injection, and handling circular dependencies in TypeScript applications

// interfaces/email-service.interface.ts export interface EmailService { sendEmail(to: string, subject: string, body: string): Promise; }

// services/user-notification.service.ts import { injectable, inject } from 'inversify'; import { UserService } from '../interfaces/user-service.interface'; import { EmailService } from '../interfaces/email-service.interface'; import { Logger } from '../interfaces/logger.interface';

@injectable() export class UserNotificationService { constructor( @inject('UserService') private readonly userService: UserService, @inject('EmailService') private readonly emailService: EmailService, @inject('Logger') private readonly logger: Logger ) { // Validate required dependencies if (!userService) throw new Error('UserService is required'); if (!emailService) throw new Error('EmailService is required'); if (!logger) throw new Error('Logger is required'); }

async notifyUser(userId: string, message: string): Promise { const user = await this.userService.findById(userId); await this.emailService.sendEmail(user.email, 'Notification', message); this.logger.info(Notification sent to user ${userId}); } }

</example>

<example type="property-injection">
```typescript
// services/analytics.service.ts
import { injectable, inject, optional } from 'inversify';
import { MetricsCollector } from '../interfaces/metrics-collector.interface';
import { CacheService } from '../interfaces/cache-service.interface';

@injectable()
export class AnalyticsService {
  // Optional dependency via property injection
  @inject('MetricsCollector') @optional()
  private metricsCollector?: MetricsCollector;

  // Required dependency via constructor
  constructor(
    @inject('CacheService') private readonly cacheService: CacheService
  ) {
    if (!cacheService) throw new Error('CacheService is required');
  }

  async trackEvent(event: string, data: any): Promise<void> {
    // Use optional dependency if available
    if (this.metricsCollector) {
      await this.metricsCollector.record(event, data);
    }
    
    // Always use required dependency
    await this.cacheService.set(`event:${event}`, data);
  }
}

Read the full file on GitHub · 212 lines

Changes

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.

  1. 3d ago First seen · 212 lines · 13 tokens per session scan A ce055fe05d77

Subscribe to this mod's changes

dependency-injection is a cursor rule published in the GitHub repository jahands/prompts (19 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 1,421 once invoked, about $0.0001 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.