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/AGENTS.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/instructions/thedevelobear/react-rewards/agents-md)<a href="https://agentmods.dev/instructions/thedevelobear/react-rewards/agents-md"><img src="https://agentmods.dev/badge/instructions/thedevelobear/react-rewards/agents-md/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/instructions/thedevelobear/react-rewards/agents-md"><img src="https://agentmods.dev/badge/instructions/thedevelobear/react-rewards/agents-md.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.01967 | $0.01967 |
| Opus 5.5 | $0.00787 | $0.00787 |
| Sonnet 5.5 | $0.00393 | $0.00393 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
react-rewards AGENTS.md 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
react-rewards is a small React library of reward micro-interactions (confetti, emoji, balloons, fireworks). Version 3 is a rewrite around a particle engine, built PR by PR in the v3 plan.
Before you start
- Read
docs/README.md, then the active plan it links to, if there is one. - Check
docs/decisions/for anything your change touches. Don't silently re-decide something recorded there. If a decision needs to change, propose a new ADR. For the preview site, also readdemo/README.md.
Starting a branch
Every change is a branch made from master, merged into it through a PR (ADR 0056).
- Run
git fetch. If your work already has a branch, continue on it. Otherwise create one frommasterwithout tracking it, named after the change's main commit type and its topic:
Withoutgit switch --no-track -c feat/topic origin/master--no-track, git makesmasterthe branch's upstream. A plain push, including VS Code's Push button, then lands the commits onmasterwith no PR. When the maintainer asks for a push, usegit push -u origin feat/topic. - Bring the docs up to date with what has merged, in the first commit of the new branch. Set any ADR left as "Proposed" by a merged PR to "Accepted" (unless the maintainer changed it). If a plan lists a merged PR as "In review", mark it "Merged" with its PR number. If that was the plan's last PR, mark the plan done.
- When the work is done, stop and report to the maintainer. Don't push branches or open PRs unless the maintainer asks.
Work over several PRs
Work too big for one PR gets a plan in docs/plans/, with a progress table, as v3 did. Each PR in the table is usually done in a fresh session:
- Find the first PR in the progress table that isn't merged, and start or continue its branch as above.
- Before writing code, ask the maintainer the open questions the plan assigns to this PR. Record each answer as an ADR (or in
demo/README.md, if it is about the site's design), and remove the question from the table. - When the PR is done, set its status to "In review".
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 · +2 tokens per session 581cb9bf07b7
- 3d ago First seen · 61 lines · 1,965 tokens per session scan A 01fbfe8e6d34
react-rewards AGENTS.md is an instructions file published in the GitHub repository thedevelobear/react-rewards (1,678 stars, last pushed 2d ago), licensed MIT. It adds 1,967 tokens to every session, about $0.0079 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.