new-event-handler

new-event-handler is a command for GitHub Copilot from srnichols/plan-forge. It costs 19 tokens per session (643 once invoked), scanned A, original, MIT.

A command that creates domain events and MediatR handlers in .NET. A domain event is a message saying that something important happened in the application, while a handler contains the response to that message.

In plain words
What is it for?
Use it to publish typed events such as an order being placed and trigger work such as sending email and writing logs.
Why use it?
It separates the code that records an event from the code that reacts to it, so additional reactions can be added without putting them all in one operation.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

Good fit Use it to publish typed events such as an order being placed and trigger work such as sending email and writing logs.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/srnichols/plan-forge/new-event-handler
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.

Clone the repo
git clone --depth 1 https://github.com/srnichols/plan-forge

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for new-event-handler

README.md
[![agentmods](https://agentmods.dev/badge/commands/srnichols/plan-forge/new-event-handler/github.svg)](https://agentmods.dev/commands/srnichols/plan-forge/new-event-handler)
Your own site
<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-event-handler"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-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.

agentmods 80×15 button for new-event-handler

Your own site · 80×15
<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-event-handler"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-event-handler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00019 $0.00643
Opus 5 $0.00010 $0.00321
Sonnet 5 $0.00004 $0.00129
Haiku 4.5 $0.00002 $0.00064

Measured today against content hash 18b2a5361f06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

new-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 today.

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.

presets/dotnet/.github/prompts/new-event-handler.prompt.md · 106 lines

How it starts

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

Create New Event Handler

Scaffold domain events with typed handlers using MediatR notifications.

Required Pattern

Domain Event

// Marker interface for domain events
public interface IDomainEvent : INotification
{
    Guid EventId { get; }
    DateTime OccurredAt { get; }
}

// Base record for convenience
public abstract record DomainEvent : IDomainEvent
{
    public Guid EventId { get; } = Guid.NewGuid();
    public DateTime OccurredAt { get; } = DateTime.UtcNow;
}

// Concrete event
public record OrderPlacedEvent(
    Guid OrderId,
    Guid CustomerId,
    decimal TotalAmount) : DomainEvent;

Event Handler

public class OrderPlacedHandler : INotificationHandler<OrderPlacedEvent>
{
    private readonly IEmailService _emailService;
    private readonly ILogger<OrderPlacedHandler> _logger;

    public OrderPlacedHandler(IEmailService emailService, ILogger<OrderPlacedHandler> logger)
    {
        _emailService = emailService;
        _logger = logger;
    }

    public async Task Handle(OrderPlacedEvent notification, CancellationToken ct)
    {
        _logger.LogInformation("Handling OrderPlaced: {OrderId}", notification.OrderId);
        await _emailService.SendOrderConfirmationAsync(notification.OrderId, ct);
    }
}

Publishing Events

public class OrderService
{
    private readonly IMediator _mediator;

    public async Task<Order> PlaceOrderAsync(CreateOrderRequest request, CancellationToken ct)
    {
        var order = new Order(request.CustomerId, request.Items);
        await _repository.AddAsync(order, ct);

        await _mediator.Publish(new OrderPlacedEvent(
            order.Id, order.CustomerId, order.TotalAmount), ct);

        return order;
    }
}

Multiple Handlers per Event

// MediatR publishes to ALL registered handlers for an event
public class OrderPlacedAuditHandler : INotificationHandler<OrderPlacedEvent>
{
    public async Task Handle(OrderPlacedEvent notification, CancellationToken ct)
    {
        // Write to audit log — runs independently of email handler
    }
}

Read the full file on GitHub · 106 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. today First seen · 106 lines · 19 tokens per session scan A 18b2a5361f06

Subscribe to this mod's changes

new-event-handler is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 643 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-09-08.