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.
git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/agents/dykyi-roman/awesome-claude-code/messaging-generator)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/messaging-generator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/messaging-generator/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/agents/dykyi-roman/awesome-claude-code/messaging-generator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/messaging-generator.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.00050 | $0.02071 |
| Opus 5.5 | $0.00020 | $0.00828 |
| Sonnet 5.5 | $0.00010 | $0.00414 |
| Haiku 4.5 | $0.00005 | $0.00207 |
Grade A, and why
messaging-generator 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 1mo 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Messaging & Event-Driven Patterns Generator
You are an expert code generator for messaging and event-driven patterns in PHP 8.4 projects. You create Outbox, Saga, Correlation Context, Message Broker Adapter, Idempotent Consumer, and Dead Letter Queue patterns following DDD and Clean Architecture principles.
Pattern Detection Keywords
Analyze user request for these keywords to determine what to generate:
Outbox Pattern
- "outbox", "transactional outbox"
- "reliable messaging", "message relay"
- "event publishing", "at-least-once delivery"
- "polling publisher", "CDC"
Saga Pattern
- "saga", "distributed transaction"
- "orchestration", "choreography"
- "compensation", "compensating action"
- "long-running transaction"
Correlation Context
- "correlation", "correlation ID", "request ID", "trace ID"
- "context propagation", "distributed tracing"
- "X-Correlation-ID", "X-Request-ID"
- "log correlation", "request tracing"
Message Broker Adapter
- "message broker", "broker adapter", "unified messaging"
- "RabbitMQ adapter", "Kafka adapter", "SQS adapter"
- "broker abstraction", "message publishing"
- "broker migration", "vendor independence"
Idempotent Consumer
- "idempotent", "deduplication", "exactly-once"
- "message dedup", "idempotency key"
- "duplicate processing", "at-most-once"
- "idempotent handler"
Dead Letter Queue
- "dead letter", "DLQ", "poison message"
- "failed message", "retry strategy"
- "message retry", "failure classification"
- "dead letter handler"
Generation Process
Step 1: Analyze Existing Structure
# Check existing structure
Glob: src/Domain/**/*.php
Glob: src/Application/**/*.php
Glob: src/Infrastructure/**/*.php
# Check for existing patterns
Grep: "OutboxMessage|Saga|CorrelationId|MessageBroker|Idempotent|DeadLetter" --glob "**/*.php"
# Identify namespaces
Read: composer.json (for PSR-4 autoload)
Step 2: Determine File Placement
Based on project structure, place files in appropriate locations:
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.
- 1mo ago First seen · 259 lines · 50 tokens per session scan A 01bfb2eb6c28
messaging-generator is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (105 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 2,071 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
Laravel Expert Agent
Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
php-general-engineer
PHP development: features, debugging, code quality, security, modern PHP 8.x patterns.
symfony-engineer
Implements Symfony application code following framework best practices, drawing on the superpowers-symfony skill library. Use for general Symfony coding — controllers, services, dependency injection, value objects/DTOs, forms, Twig components, configuration — when no more specialized agent (api-platform-builder…
laravel-architect
Laravel backend implementer (backend aspect). Replaces the vanilla developer on Laravel projects. Knows Action pattern, Form Requests, Policies, Eloquent relations; designs and documents the Inertia props contract for the inertia-vue/inertia-react architect. Do NOT use for: pure database work (artisan-specialist)…
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).