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-dotnet-api/agents-mdgit clone --depth 1 https://github.com/OneSignal/onesignal-dotnet-apiWrote 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/onesignal/onesignal-dotnet-api/agents-md)<a href="https://agentmods.dev/instructions/onesignal/onesignal-dotnet-api/agents-md"><img src="https://agentmods.dev/badge/instructions/onesignal/onesignal-dotnet-api/agents-md.svg" alt="Measured on agentmods" 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 | $0.00865 | $0.00865 |
| Opus 5 | $0.00432 | $0.00432 |
| Sonnet 5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
onesignal-dotnet-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 4d 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.
- 4d ago First seen · 84 lines · 865 tokens per session scan A 26f3ce5c239d
onesignal-dotnet-api AGENTS.md is an instructions file published in the GitHub repository OneSignal/onesignal-dotnet-api (23 stars, last pushed 6d ago), with no licence file. It adds 865 tokens to every session, about $0.0043 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
maui public-api.instructions.md
Instructions for dotnet/maui, covering public api surface design, api addition rules, publicapi.unshipped.txt, obsolescence and removal and visibility decisions.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
moorestech AGENTS.md
AGENTS.md instructions for moorestech/moorestech, covering コーディングの指針, qa（必須）, 互換性とパフォーマンス, 既知の制約（設計上の割り切り） and regionの活用.
bitfinex-net
Use Bitfinex.Net when generating C#/.NET code that interacts with Bitfinex, including Spot, margin, derivatives symbols, funding, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on Bitfinex integration requests in C#, .NET, dotnet, F#, or VB.NET context.
Bitfinex.Net copilot-instructions.md
Instructions for JKorf/Bitfinex.Net, covering copilot instructions for bitfinex.net, use bitfinex.net, not raw http, client setup, result handling and api structure.
coinex-net
Use CoinEx.Net when generating C#/.NET code that interacts with the CoinEx cryptocurrency exchange, including Spot V2, margin account operations, futures, REST endpoints, WebSocket subscriptions, account management, market data, or order placement. Triggers on requests mentioning CoinEx integration in C#, .NET…