Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/packages/.github/instructions/packmind-domain-events.instructions.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/instructions/packmindhub/packmind/packmind-domain-events)<a href="https://agentmods.dev/instructions/packmindhub/packmind/packmind-domain-events"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-domain-events.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.00266 | $0.00266 |
| Opus 5 | $0.00133 | $0.00133 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
packmind packmind-domain-events.instructions.md 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 3d 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.
What it actually says
Standard: Domain Events
Domain events enable communication between hexas without creating direct dependencies. Apply these rules when creating events, emitting them, or implementing listeners to react to events from other do... :
- Define event classes in
packages/types/src/{domain}/events/with anindex.tsbarrel file - Define payload as a separate
{EventName}Payloadinterface - Extend
PackmindListener<TAdapter>and implementregisterHandlers()to subscribe to events - Extend
UserEventfor user-triggered actions,SystemEventfor background/automated processes - Include
userIdandorganizationIdin UserEvent payloads; includeorganizationIdin SystemEvent payloads when applicable - Suffix event class names with
Event(e.g.,StandardUpdatedEvent) - Use
eventEmitterService.emit(new MyEvent(payload))to emit events - Use
static override readonly eventNamewithdomain.entity.actionpattern - Use
this.subscribe(EventClass, this.handlerMethod)to register handlers - Use arrow functions for handlers to preserve
thisbinding
Full standard is available here for further request: Domain Events
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.
- 3d ago First seen · 18 lines · 266 tokens per session scan A dcd46ea571b7
packmind packmind-domain-events.instructions.md is an instructions file published in the GitHub repository PackmindHub/packmind (309 stars, last pushed today), licensed Apache-2.0. It adds 266 tokens to every session, about $0.0013 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-03.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge auth.instructions.md
.NET authentication & authorization — JWT/OIDC, policy-based auth, multi-tenant isolation, API keys, testing.
plan-forge api-patterns.instructions.md
API patterns for .NET — REST conventions, ProblemDetails, pagination, versioning, error responses.
plan-forge graphql.instructions.md
GraphQL patterns for .NET — Hot Chocolate, code-first schema, DataLoaders, authorization, multi-tenant resolvers.
plan-forge messaging.instructions.md
Messaging patterns for .NET — Dapr Pub/Sub, MassTransit, NATS, RabbitMQ, CloudEvents.
plan-forge errorhandling.instructions.md
Error handling patterns — Exception hierarchy, ProblemDetails responses, error boundaries, global exception middleware.