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 avizmarlon/agent-skills --skill reactive-integration-designgit clone --depth 1 https://github.com/avizmarlon/agent-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/avizmarlon/agent-skills/reactive-integration-design)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/reactive-integration-design"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/reactive-integration-design/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/skills/avizmarlon/agent-skills/reactive-integration-design"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/reactive-integration-design.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.00068 | $0.01036 |
| Opus 5 | $0.00034 | $0.00518 |
| Sonnet 5 | $0.00014 | $0.00207 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
reactive-integration-design 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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observe Facts, Not Promises — Reactive Integration Design
When designing a reactive integration to an external system event (container deployment, Kubernetes state change, queue message, OS-level file change), prefer primitive event streams (kernel-level or runtime-level — docker events, inotify, Kubernetes watch API, fanotify, journald) over application-level callbacks (webhooks, SDK callbacks, HTTP API polling).
Why This Matters
Primitive events describe facts. They are generated by the kernel or runtime and represent something that actually occurred in the system. The contract between your integration and the event source is stable across versions because it is enforced at the infrastructure layer, not the application layer.
Webhooks describe promises. They are contracts the application makes to notify you when something happens. Promises break silently:
- When the application upgrades, the webhook payload format may change without notice.
- When the application loses permissions or encounters errors, events get dropped without notification.
- Under high load, the application may batch, skip, or defer webhook deliveries.
- The webhook endpoint itself may be removed or behavior changed without backward compatibility.
The fragility gap: a webhook depends on the application continuing to implement and maintain the notification contract. A primitive event stream depends only on the infrastructure remaining functional—which it must, or the entire system fails anyway.
Examples
- Container deployment monitoring: Instead of polling the Kubernetes API every N seconds or relying on a platform's webhook delivery, consume the Kubernetes watch API directly. The watch API is a runtime primitive; a platform's webhook system is an application-level contract that can change.
- File system integration: Instead of consuming an application's "file changed" callback, use
inotify(Linux) orfanotify(Linux, more recent) to observe kernel-level file events. These are OS primitives. - Container lifecycle: Instead of relying on a container orchestration platform's webhook, consume
docker eventsdirectly.docker eventsis a runtime primitive exposed by the Docker daemon. - Journal events: Instead of polling application logs via HTTP API, follow
journaldon the host. Journal is kernel-level infrastructure.
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.
- 12d ago First seen · 66 lines · 68 tokens per session scan A ea4d7358750a
reactive-integration-design is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 1,036 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
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
django-security
Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.