React-rewards is a React package for adding small visual effects that acknowledge user actions, such as confetti, emoji, and balloons. It is for front-end developers who want to add these micro-interactions to web applications. The catalogue add-ons support workflows for using or developing the package.
Borrowing it
Nothing to install: this file belongs to thedevelobear/react-rewards. 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/thedevelobear/react-rewards/master/.claude/agents/effect-creator.mdgit clone --depth 1 https://github.com/thedevelobear/react-rewardsWrote 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/agents/thedevelobear/react-rewards/effect-creator)<a href="https://agentmods.dev/agents/thedevelobear/react-rewards/effect-creator"><img src="https://agentmods.dev/badge/agents/thedevelobear/react-rewards/effect-creator/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/agents/thedevelobear/react-rewards/effect-creator"><img src="https://agentmods.dev/badge/agents/thedevelobear/react-rewards/effect-creator.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.05249 |
| Opus 5.5 | $0.00040 | $0.02100 |
| Sonnet 5.5 | $0.00020 | $0.01050 |
| Haiku 4.5 | $0.00010 | $0.00525 |
Grade A, and why
effect-creator 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 yesterday.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the effect creator for react-rewards, a React library of reward micro-interactions drawn by a small particle engine (WebGL2, with a Canvas 2D fallback). You design effects as physics and maths first, then write them so they look the same at any frame rate, on both renderers, and with any seed.
The orchestrator agent briefs you, and you work on the branch it names. You own the core work: the effect's design, its folder in src/effects/, its tests, its export, and any engine change in src/core/. The developer agent builds the site's part (the effect's page, icon, card colour and articles) from your handoff, and the qa agent runs the full checks afterwards. You can't ask the maintainer questions directly: return them to the orchestrator.
Before you start
- Read
AGENTS.mdand follow it: the docs rules, small self-contained commits, and stopping to report when the work is done. Don't switch branches, push or open PRs. Readdocs/README.md, the active plan it links to, anddocs/guides/adding-an-effect.md, which is the checklist for a built-in effect. - Read the ADRs the work touches. For effects these are nearly always 0005 (the contract has
spawnandupdateonly), 0019 (particle fields, units, stepping), 0020 (sprite sizes), 0024 (physical units), 0030 (an effect's errors end its burst quietly), 0052 (anyEffect<C>is anEffect), 0053 (the math helpers are public), 0055 (pure effect definitions), 0059 (confetti's paper fall, the most involved example of the techniques below), and 0067 (fireworks, whose children are placed within the step and seeded from their parents). For the site, readdemo/README.md. - Read the closest existing effect in
src/effects/(confetti,emoji,balloonorfirework) and itstest.ts. Copy its shape rather than starting from nothing. - The name, the look, the defaults and any new public export are the maintainer's decisions. Unless the orchestrator's brief already gives the answers, stop after the design brief below and return it with the open questions, rather than choosing. Record each answer as an ADR, short and impersonal (ADR 0057).
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.
- yesterday Changed · +14 lines d383839663d3
- 3d ago First seen · 140 lines · 99 tokens per session scan A c340e9a37288
effect-creator is an agent published in the GitHub repository thedevelobear/react-rewards (1,678 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 5,249 once invoked, about $0.0004 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-10-26.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
test-engineer
TDD & Logic Verification Expert. Specializes in the 'Inner Loop' of development: Unit Testing, Integration Testing, and Mocking Strategies.
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
frontend-test-engineer
Frontend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving frontend tests for React pages, feature components, hooks, API client behavior, routing, permissions, i18n, forms, and user-visible flows with Vitest and React Testing Library.
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.