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 makigjuro/cloudstack-ai-plugins --skill add-event-handlergit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWrote 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/makigjuro/cloudstack-ai-plugins/add-event-handler)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/add-event-handler"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/add-event-handler/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/makigjuro/cloudstack-ai-plugins/add-event-handler"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/add-event-handler.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.00045 | $0.01006 |
| Opus 5.5 | $0.00018 | $0.00402 |
| Sonnet 5.5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
add-event-handler 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Event Handler
When the user asks to add an event handler, scaffold a WolverineFx handler for a domain or integration event.
Arguments
{EventName}-- Name of the event to handle (e.g.,OrderCreatedEvent){Service}-- Target microservice (ask if ambiguous)
Configuration
Read cloudstack.json from the project root at the start of execution. Extract:
NAMESPACE=project.namespace(default: detect from*.slnname or first*.csprojroot namespace)DOMAIN_PATH=backend.sharedDomainPath(default: find directory matching**/Domain/containingEntities/)SERVICES=backend.services[](default: discover fromsrc/*/directories containing.Application/subfolders)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
1. Find the Event
Search for the event class:
grep -rn "class {EventName}" src/
If the event doesn't exist, suggest running /add-entity first or create it inline.
2. Event Handler (Application/Events/{EventName}Handler.cs)
namespace {Namespace}.{Service}.Application.Events;
public class {EventName}Handler
{
// Constructor-inject repositories, services, or ILogger<T>
public async Task Handle({EventName} @event, CancellationToken cancellationToken)
{
// React to the event:
// - Update read models
// - Send notifications
// - Publish integration events
// - Trigger side effects
}
}
For handlers that publish to a message broker:
public class {EventName}Handler
{
private readonly IMessagePublisher _messagePublisher;
private readonly ILogger<{EventName}Handler> _logger;
public {EventName}Handler(IMessagePublisher messagePublisher, ILogger<{EventName}Handler> logger)
{
_messagePublisher = messagePublisher;
_logger = logger;
}
public async Task Handle({EventName} @event, CancellationToken cancellationToken)
{
_logger.LogInformation("Handling {Event} for {Id}", nameof({EventName}), @event.Id);
await _messagePublisher.PublishAsync(
"{domain}.events.{event-type}",
@event,
cancellationToken);
}
}
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 · 135 lines · 45 tokens per session scan A 3102e06c40a8
add-event-handler is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,006 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-31.
Other skills, from other repositories
gateway-api
Migrate from the retired ingress-nginx controller to Kubernetes Gateway API, and design, debug, and review Gateway API ingress. Covers annotation inventory and risk triage, ingress2gateway conversion, implementation choice (Envoy Gateway default, Cilium, Istio, NGINX Gateway Fabric, AWS Load Balancer Controller), CRD…
python-services
Python patterns for CLI tools, async parallelism, and backend services. Use when building CLI apps, async/parallel Python, FastAPI services, background jobs, or configuring Python project tooling (uv, ruff, ty).
nodejs-backend
Node.js backend patterns: framework selection, layered architecture, TypeScript, validation, error handling, security, production deployment. Use when building REST APIs, Express/Fastify servers, microservices, or server-side TypeScript.
document
Generate, format, and validate code documentation — docstrings, JSDoc, OpenAPI/Swagger specs, documentation sites, and developer guides.
mcp
MCP server and client development — scaffold, implement tools/resources/prompts, validate schemas, debug protocol compliance, and deploy with auth and rate limiting.
ia-php-laravel
Modern PHP 8.4 and Laravel patterns: architecture, Eloquent, migrations, queues, testing. Use when working with Laravel, Eloquent, Blade, artisan, or building/testing a framework-based PHP app. Not for php-src internals, standalone PHP libraries, or general PHP language discussion.