Borrowing it
Nothing to install: this file belongs to rolandjitsu/react-fetch-streams. 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/rolandjitsu/react-fetch-streams/master/AGENTS.mdgit clone --depth 1 https://github.com/rolandjitsu/react-fetch-streamsWrote 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/rolandjitsu/react-fetch-streams/agents-md)<a href="https://agentmods.dev/instructions/rolandjitsu/react-fetch-streams/agents-md"><img src="https://agentmods.dev/badge/instructions/rolandjitsu/react-fetch-streams/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/rolandjitsu/react-fetch-streams/agents-md"><img src="https://agentmods.dev/badge/instructions/rolandjitsu/react-fetch-streams/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.01176 | $0.01176 |
| Opus 5.5 | $0.00470 | $0.00470 |
| Sonnet 5.5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
react-fetch-streams 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 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents in this repo. Human contributors: see the Contribute section of the README.
This is react-fetch-streams: React hooks for streaming a response body over the Fetch + Streams
APIs (useStream, plus useNdjsonStream for newline-delimited JSON) and for Server-Sent Events
(useEventSource, useEventStream). It is a small,
dependency-free, published npm library written in TypeScript. Keep it that way; think twice before
adding a runtime dependency.
The toolchain is the Rust-based oxc stack: oxlint to lint,
Prettier to format, tsdown (Rolldown + oxc) to
build and emit declarations, and Vitest to test; TypeScript (tsc --noEmit)
type-checks. There is no Babel, ESLint, or Rollup; do not reintroduce them.
Workflow
- Clarify the design before implementing. For anything non-trivial, agree on the approach first.
- One unit of change per commit. Never mix unrelated changes. Present the change for review before committing.
- Every change ships with tests. Run local CI before calling it done, and do not claim it passes without running it.
- Verify against the code and the tools: read before you answer, run before you assert.
Local CI (must be green before review):
npm run typecheck # tsc --noEmit
npm run lint # oxlint
npm run format:check # prettier
npm run build # tsdown
npm run test:cov # vitest
Writing: code, comments, docs, commits
- Concise and to the point. No fluff. Explain the non-obvious; do not narrate the obvious.
- ASCII only. No em-dash and no
--; write-. Use->not the arrow glyph,!=not the not-equal glyph, and so on. - Comments justify why, not what. Delete any comment that restates the code.
- Formatting is not a matter of taste: Prettier owns it. Run
npm run formatrather than hand-formatting. House style (.prettierrc.json) is single quotes, no trailing commas, no bracket spacing, and arrow parens omitted when possible.
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 · 96 lines · 1,176 tokens per session scan A 3b1e44f90281
react-fetch-streams AGENTS.md is an instructions file published in the GitHub repository rolandjitsu/react-fetch-streams (11 stars, last pushed 5d ago), licensed MIT. It adds 1,176 tokens to every session, about $0.0047 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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.