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 JBorgia/signaltree --skill eventsgit clone --depth 1 https://github.com/JBorgia/signaltreeWrote 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/jborgia/signaltree/events)<a href="https://agentmods.dev/skills/jborgia/signaltree/events"><img src="https://agentmods.dev/badge/skills/jborgia/signaltree/events/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/jborgia/signaltree/events"><img src="https://agentmods.dev/badge/skills/jborgia/signaltree/events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00139 | $0.02446 |
| Opus 5.5 | $0.00056 | $0.00978 |
| Sonnet 5.5 | $0.00028 | $0.00489 |
| Haiku 4.5 | $0.00014 | $0.00245 |
Grade A, and why
signaltree-events 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 2mo 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using @signaltree/events
Use when an app needs typed event contracts with runtime validation, stable IDs/correlation, idempotency, and retry semantics across a process boundary (queue, WebSocket, service bus). Skip for local in-process emitters.
Three layers, composable independently:
- Schema + validation —
createEventSchema,parseEvent(THROWS),safeParseEvent(returns a result),isValidEvent(type guard). Names match Zod'sparse/safeParse; before 14.1.1 they were inverted. - Registry + factory —
EventRegistry,createEventFactory - Transport adapters (subpath) —
/nestjs(BullMQ/Redis),/angular(WebSocket bridge),/testing(MockEventBus)
Install:
npm install @signaltree/events zod
Zod is required at runtime even without authoring schemas. Peer: zod ^3 || ^4 required. Optional peers (install only what you use): @angular/core ^18+, rxjs ^7, @nestjs/common ^10||^11, bullmq ^5, reflect-metadata ^0.1||^0.2. Angular range is ^18 (broader than rest of SignalTree). ESM-only — use dynamic import() in CommonJS consumers.
Define a schema:
import { createEventSchema, z } from '@signaltree/events';
// createEventSchema: type string + Zod raw shape (field map)
// createEventSchemaFromZod: type string + already-built ZodObject
export const UserCreatedSchema = createEventSchema('user.created', {
id: z.string().uuid(),
email: z.string().email(),
name: z.string().min(1),
});
export type UserCreated = z.infer<typeof UserCreatedSchema>;
Validate:
import { createEventSchema, isValidEvent, parseEvent, safeParseEvent, z } from '@signaltree/events';
declare const incoming: unknown;
const UserCreatedSchema = createEventSchema('user.created', {
id: z.string().uuid(),
email: z.string().email(),
name: z.string().min(1),
});
if (isValidEvent(UserCreatedSchema, incoming)) {
/* typed */
}
const event = parseEvent(UserCreatedSchema, incoming); // throws on fail
const result = safeParseEvent(UserCreatedSchema, incoming); // never throws; result.success + result.error.issues
Factory (source and environment required; systemActor.type must be 'user'|'system'|'admin'|'webhook'):
import { createEventFactory } from '@signaltree/events';
const factory = createEventFactory<UserCreated>({
source: 'api-gateway',
environment: 'production',
systemActor: { type: 'system', id: 'api-gateway' },
});
const created = factory.create('user.created', { id: crypto.randomUUID(), email: '[email protected]', name: 'Ada Lovelace' });
Retry + idempotency (defaultTtlMs, not ttlMs; check takes (event, consumer, options?)):
import { classifyError, isRetryableError, InMemoryIdempotencyStore, BaseEvent } from '@signaltree/events';
declare const incomingEvent: BaseEvent<string, unknown>;
declare function processEvent(e: BaseEvent<string, unknown>): Promise<void>;
try {
await processEvent(incomingEvent);
} catch (err) {
if (isRetryableError(err)) {
/* enqueue retry */
}
}
const store = new InMemoryIdempotencyStore({ defaultTtlMs: 60_000 });
const result = await store.check(incomingEvent, 'welcome-email-subscriber');
if (result.isDuplicate) return;
InMemoryIdempotencyStore is process-local — use Redis-backed store for multi-instance deployments.
NestJS (/nestjs subpath — requires @nestjs/common, bullmq, reflect-metadata):
import { EventBusModule } from '@signaltree/events/nestjs';
@Module({
imports: [EventBusModule.forRoot({ redis: { host: 'localhost', port: 6379 }, preset: 'priority-based' })],
})
export class AppModule {}
Subscribers extend BaseSubscriber<T> with config: SubscriberConfig (name, eventTypes, priority, concurrency) and handle(event): Promise<ProcessingResult>.
Use forRootAsync when Redis config requires async loading.
Angular entityMap bridge (/angular subpath, v13+) — for apps holding entities in a @signaltree/core entityMap, don't hand-write a per-event upsertOne/updateOne/removeOne loop over an event batch; entityEventHandler maps the batch onto entityMap's own batch ops (one upsertMany/updateMany/removeMany call, not one per event):
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.
- 2mo ago First seen · 199 lines · 139 tokens per session scan A a278d74bc9c0
signaltree-events is a skill published in the GitHub repository JBorgia/signaltree (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 139 tokens to every session and 2,446 once invoked, about $0.0006 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-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…