integration-event SKILL.md skillA
integration-event from gbourgeat/ddd-ts-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gbourgeat/ddd-ts-kit/integration-event@git:20261017.50437f5Pins git:20261017.50437f5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gbourgeat/ddd-ts-kit
- Path
plugin/skills/integration-event/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261017.50437f5, committed Oct 17, 2026
- First version recorded
- Oct 10, 2026
- Size
- 5,414 bytes
- Repository stars
- 7
- License
- MIT
Makes two bounded contexts collaborate through a versioned integration event: declaring it in the producer's published language, publishing through the outbox, handling it idempotently in the consumer, evolving its payload, choosing a broker. Use when a context must react to another, when building a contract row of the slices, or when the user mentions events between contexts, messaging, outbox, consumers, RabbitMQ, Kafka, NATS, Redis Streams or eventual consistency. To decide who is upstream…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Integration events
Event under discussion: `$ARGUMENTS`
A domain event stays inside its context. What crosses a boundary is an integration event: a
contract the producer owns, in its `published-language/`, the only folder another context
may import.
## Publish (producer side)
```bash
npx ddd-ts-kit generate integration-event <ctx> <Aggregate> <Fact> --json
```
writes the declaration `published-language/<fact>.v1.integration-event.ts`
(`defineIntegrationEvent({ type, version, payload })`), its export, the publisher in
`application/integration/publishers/` (a reaction to the domain event, which it creates when
missing; always in the default `before-commit` phase, so the outbox row commits with the state
change) and the specs. Fill the `next` places:
- **Name**: `<context>.<aggregate>.<fact>`, past tense (`events/name-format`).
- **Payload**: what a consumer needs to act without calling back, and nothing internal:
identifiers and facts, not the aggregate as JSON; no personal data unless a consumer needs
it. Describe each field in the schema: the description lands in the catalog.
- **Outbox**: with a database the event is written in the transaction of the command and
…Read the whole file at its exact version.
How to install
mdr add gbourgeat/ddd-ts-kit/integration-event@sha256:7aac444755bcc93cThe line at the top of this page pins the label git:20261017.50437f5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6qhorpfdmn3ddgv7)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Oct 10, 2026 and Oct 17, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.50437f5 latest | 2026-10-17 | 50437f5 | 5,414 B | A | view · diff |
| git:20261015.55b91ed | 2026-10-15 | 55b91ed | 4,974 B | A | view · diff |
| git:20261010.5f1fa41 | 2026-10-10 | 5f1fa41 | 4,791 B | A | view · diff |
| git:20261010.9ecedeb | 2026-10-10 | 9ecedeb | 4,697 B | A | view · diff |
| git:20261010.c6c87e0 | 2026-10-10 | c6c87e0 | 4,579 B | A | view · diff |
| git:20261010.ec77307 | 2026-10-10 | ec77307 | 4,436 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5414 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gbourgeat/ddd-ts-kit · 7 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6qhorpfdmn3ddgv7 GET https://markdownregistry.com/api/v1/resolve?ref=gbourgeat/ddd-ts-kit/integration-event GET https://markdownregistry.com/api/v1/blob/7aac444755bcc93ce575261d075e2fb9e250485c80ecf4238e10718251b92dd1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.