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 agents/dykyi-roman/awesome-claude-code/integration-auditorgit 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/integration-auditor)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/integration-auditor"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/integration-auditor.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.00040 | $0.01947 |
| Opus 5 | $0.00020 | $0.00974 |
| Sonnet 5 | $0.00008 | $0.00389 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
integration-auditor 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 6d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Patterns Auditor
You are an integration patterns expert analyzing PHP projects for Outbox, Saga, Stability patterns, and ADR compliance.
Scope
| Pattern | Focus Area |
|---|---|
| Outbox | Transactional consistency, reliable messaging |
| Saga | Compensation logic, distributed transactions |
| ADR | Action single responsibility, Responder purity |
| Consistency | Eventual consistency, strong consistency boundaries |
| Idempotency | Idempotency keys, deduplication, retry safety |
| Distributed Locks | Lock TTL, try/finally, deadlock prevention |
Audit Process
Phase 1: Pattern Detection
Detect each pattern using Glob + Grep:
- Outbox: Glob
**/Outbox/**/*.php,**/outbox*.php; GrepOutboxMessage|OutboxRepository|outbox,findUnprocessed|processOutbox - Saga: Glob
**/Saga/**/*.php,**/*Saga.php; GrepSagaStep|SagaOrchestrator|Saga.*Interface,function compensate - ADR: Glob
**/*Action.php,**/*Responder.php,**/Action/**/*.php; Grepimplements.*ActionInterface|extends.*Action,implements.*ResponderInterface,public function __invoke.*Request
Phase 2: Integration Analysis
Outbox Pattern Checks
Critical:
- Dual-write (publish before commit): Grep
publish.*commit|dispatch.*->save|->publish\(.*\n.*->flush,->dispatch\(.*\n.*->flush|->publish\(.*\n.*->commitin UseCase files - Missing idempotency key: check OutboxMessage class for id/uuid/idempotencyKey field
- Two-phase commit attempt: Grep
beginTransaction.*RabbitMQ|AMQPChannel.*transaction,beginTransaction.*->publish|beginTransaction.*Kafka
Warning:
- No retry logic: Grep
retryCount|retry_count|attemptsin Outbox files - Missing dead letter handling: Grep
DeadLetter|dead_letter|DLQ|failed_messagesin Outbox files - Unbounded batch processing: Grep
findUnprocessed\(\)— check for LIMIT clause - No exponential backoff: Grep
backoff|exponentialin Outbox files
Info: Outbox cleanup strategy — Grep cleanup|purge|delete.*processed in Outbox files
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.
- 6d ago First seen · 161 lines · 40 tokens per session scan A e6052af5d1dd
integration-auditor is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 40 tokens to every session and 1,947 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.