react-typed-events

react-typed-events is a skill for Claude Code, Codex from stephansama/packages. It costs 63 tokens per session (895 once invoked), scanned A, a copy of data-migration, MIT.

React hooks for registering typed event listeners from the @stephansama/typed-events package. The listeners are automatically removed when a React component is unmounted.

In plain words
What is it for?
Use useListener for one event or useListeners for several events, such as updating or resetting a dashboard or drawing on a canvas.
Why use it?
It avoids manual listener cleanup and helps React components handle events whose data follows defined types.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use useListener for one event or useListeners for several events, such as updating or resetting a dashboard or drawing on a canvas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stephansama/packages/react-typed-events
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.

Any agent
npx skills add stephansama/packages --skill react-typed-events
Clone the repo
git clone --depth 1 https://github.com/stephansama/packages

Made for: Claude Code, Codex.

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 react-typed-events

README.md
[![agentmods](https://agentmods.dev/badge/skills/stephansama/packages/react-typed-events/github.svg)](https://agentmods.dev/skills/stephansama/packages/react-typed-events)
Your own site
<a href="https://agentmods.dev/skills/stephansama/packages/react-typed-events"><img src="https://agentmods.dev/badge/skills/stephansama/packages/react-typed-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.

agentmods 80×15 button for react-typed-events

Your own site · 80×15
<a href="https://agentmods.dev/skills/stephansama/packages/react-typed-events"><img src="https://agentmods.dev/badge/skills/stephansama/packages/react-typed-events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 895 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 86% copy Near-identical to another mod 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.00063 $0.00895
Opus 5.5 $0.00025 $0.00358
Sonnet 5.5 $0.00013 $0.00179
Haiku 4.5 $0.00006 $0.00089

Measured 1mo ago against content hash 2674dade9d41, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

react-typed-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 1mo 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.

Origin

This is a copy

86% identical to data-migration — 176 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.

core/typed-events/skills/react-typed-events/SKILL.md · 146 lines

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.

typed-events — React

This skill builds on typed-events. Read it first for foundational concepts including factory selection, cleanup patterns, and SSR behaviour.

Setup

import * as z from "zod";
import { createBroadcastEvent } from "@stephansama/typed-events";
import { useListeners } from "@stephansama/typed-events/react";

export const appEvents = createBroadcastEvent("my-app", {
  update: z.object({ value: z.number() }),
  reset: z.object({}),
});

Hooks and Components

useListener — single event

import { useListener } from '@stephansama/typed-events/react';
import { animationEvent } from './events';

function Canvas() {
  useListener(animationEvent, ({ data }) => {
    draw(data.x, data.y);
  });

  return <canvas />;
}

Registers the listener on mount and removes it on unmount via useEffect cleanup.

useListeners — multiple events from a map

import { useMemo } from 'react';
import { useListeners } from '@stephansama/typed-events/react';
import { appEvents } from './events';

function Dashboard() {
  const handlers = useMemo(() => ({
    update: ({ data }: { data: { value: number } }) => setValue(data.value),
    reset: () => setValue(0),
  }), []);

  useListeners(appEvents, handlers);

  return <div />;
}

Registers all handlers on mount and removes them all on unmount.

Common Mistakes

HIGH Inline listener object triggers re-registration every render

Wrong:

function MyComponent() {
  useListeners(appEvents, {
    update: ({ data }) => setValue(data.value), // new object each render
  });
}

Correct:

function MyComponent() {
  const handlers = useMemo(
    () => ({
      update: ({ data }) => setValue(data.value),
    }),
    [],
  );

  useListeners(appEvents, handlers);
}

useListeners has [map, listeners] in its useEffect dependency array. An inline object literal is a new reference every render, causing the effect to re-run: the old listener is removed and a new one is registered on every render.

Read the full file on GitHub · 146 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. 1mo ago First seen · 146 lines · 63 tokens per session scan A 2674dade9d41

Subscribe to this mod's changes

react-typed-events is a skill published in the GitHub repository stephansama/packages (5 stars, last pushed 12d ago), licensed MIT. It adds 63 tokens to every session and 895 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to data-migration, differing in 176 lines, and is treated as a copy.