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 agentmods add instructions/onesignal/onesignal-node-api/agents-mdgit clone --depth 1 https://github.com/OneSignal/onesignal-node-apiWhat 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 | $0.00729 | $0.00729 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
onesignal-node-api 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 67 lines · 729 tokens per session scan A 7626ba87de18
onesignal-node-api AGENTS.md is an instructions file published in the GitHub repository OneSignal/onesignal-node-api (52 stars, last pushed 4d ago), with no licence file. It adds 729 tokens to every session, about $0.0036 per session on Opus 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
sportsdataverse-js CLAUDE.md
Instructions for sportsdataverse/sportsdataverse-js, covering claude.md — sportsdataverse (node.js) development guide, package overview, commit convention, branches and build & development commands.
sportsdataverse-js copilot-instructions.md
Instructions for sportsdataverse/sportsdataverse-js, covering github copilot instructions — sportsdataverse (node.js), architecture (how the code is generated), conventions and commits / prs.
kavo CLAUDE.md
Claude Code instructions for kavo-labs/kavo, covering claude.md, what kavo is, commands, architecture and the request pipeline (the spine).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
core CLAUDE.md
Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.
zapo CLAUDE.md
Instructions for vinikjkkj/zapo: The contributor handbook for this repository lives in AGENTS.md. Read that file and follow it as your primary source of project conventions, architecture rules, performance constraints, and review anti-patterns.