Borrowing it
Nothing to install: this file belongs to dosco/aithy. 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/dosco/aithy/main/.claude/skills/ax-event-runtime/SKILL.mdgit clone --depth 1 https://github.com/dosco/aithyWrote 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/dosco/aithy/ax-event-runtime)<a href="https://agentmods.dev/skills/dosco/aithy/ax-event-runtime"><img src="https://agentmods.dev/badge/skills/dosco/aithy/ax-event-runtime.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.00036 | $0.01407 |
| Opus 5 | $0.00018 | $0.00704 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
ax-event-runtime 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.
This is a copy
100% identical to ax-event-runtime — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ax Event Runtime
Use this skill when an Ax program should react to notifications, webhooks, timers, queues, task completion, or application events.
Mental Model
source -> inbox -> route -> target -> stored run -> sink
Sources never call an Ax program directly. A route must explicitly choose
observe, invalidate, wake, or resume. Only the last two invoke a model.
Minimal Pattern
const source = new AxPushEventSource('application');
const target = eventTarget('triage')
.program(triageAgent)
.ai(llm)
.input((input) => input.field('incident', eventPath.data()))
.sink({ id: 'result', write: saveResult })
.build();
const events = eventRuntime({
sources: [source],
routes: [
eventRoute('incident-created')
.types('incident.created')
.wake(target)
.build(),
],
});
await events.start();
await source.publish({ event, identity, trust: 'authenticated' });
Rules
- Supply identity from authenticated adapter state, never from event data.
- Treat events without verified identity as anonymous and untrusted.
- Map event data into signature inputs; do not synthesize a user message.
- Use
eventPath.data('field')and other segment-safe selectors. Do not use dotted JSONPath strings or repurposes()as a mapping language. - Use
.project(path)only for same-name signature projection. Explicit.field()mappings override projection; missing or invalid signature inputs dead-letter before model invocation. - Use
eventInput().project(...).field(...)when a declarative mapping should be callback-free and reusable, then pass that plan to.input(),.wakeInput(), or.resumeInput(). - Callback
mapInputis an escape hatch, not a validation bypass: its result is normalized to the program signature and mapper failures dead-letter before invocation. - Use
.wakeInput()and.resumeInput()when the two actions need different contracts. Neither action silently uses the other action's mapping. - Use
observefor progress/logs andinvalidatefor catalog changes. - Use
resumeonly with an owned continuation correlation key. - Use
createProgram(instance)for stateful multi-tenant Agents. - Declare
retrySafety: 'idempotent'only when stable delivery keys protect every possible side effect. - Persist outputs before final sink delivery; redrive sink failures separately.
- Use
debounceMsandcoalesce: 'latest'only when replacing intermediate events is part of the route's declared policy. - Observe source failures with
onSourceError. - The in-memory store is volatile and single-process.
- For cooperating Node processes on one local disk, use
AxSQLiteEventStorefrom@ax-llm/ax-tools/event/sqlitewith explicit retention andcoordination: 'multi-worker'. Never recommend SQLite on a network filesystem. - Close the runtime and caller-owned protocol clients explicitly.
- Fan out to several Agents with several matching routes, not a multi-target route. This preserves independent authorization, ordering, retries, and runs.
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 · 146 lines · 36 tokens per session scan A 8c8ed96edea4
ax-event-runtime is a skill published in the GitHub repository dosco/aithy (107 stars, last pushed 6d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,407 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ax-event-runtime, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
n8n-mcp-workflows
MCP-first patterns for designing, validating, and operating n8n automations with explicit retries, failure paths, and audit trails.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…