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/malwarebo/nyrve/api-versiongit clone --depth 1 https://github.com/malwarebo/nyrveWhat 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.00263 | $0.00263 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
nyrve api-version.instructions.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.
What it actually says
The following is only required for proposed API related to chat and languageModel proposals. It's optional for other proposed API, but recommended.
When a proposed API is changed in a non-backwards-compatible way, the version number at the top of the file must be incremented. If it doesn't have a version number, we must add one. The format of the number like this:
// version: 1
No semver, just a basic incrementing integer. See existing examples in vscode.proposed.chatParticipantPrivate.d.ts (version 12), vscode.proposed.chatProvider.d.ts (version 4), and other chat/languageModel proposals. The corresponding version number in the extension's package.json must be incremented to match (you could remind the user of this if you don't have access to the extension code yourself).
An example of a non-backwards-compatible change is removing a non-optional property or changing the type to one that is incompatible with the previous type.
An example of a backwards-compatible change is an additive change or deleting a property that was already optional.
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 First seen · 19 lines · 263 tokens per session scan A d2e102d5267e
nyrve api-version.instructions.md is an instructions file published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 2mo ago), licensed MIT. It adds 263 tokens to every session, about $0.0013 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-31.
Other instructions, from other repositories
vibeyard CLAUDE.md
Instructions for elirantutia/vibeyard, covering claude.md, what this is, build & run, testing and architecture.
coder AGENTS.md
AGENTS.md instructions for coder/coder, covering coder development guidelines, task-specific guidance, workflow, essential commands and repository guardrails.
denova AGENTS.md
Instructions for alfredxw/denova, covering 项目目标, 必须遵守, 项目约定, 代码注意事项 and 前端与交互规范.
spring-plugin AGENTS.md
Instructions for explyt/spring-plugin, covering agents.md — contributor guide, project structure, build, test, run, code style and conventions and commits and pull requests.
coder CLAUDE.md
Claude Code instructions for coder/coder, a project described as: Secure environments for developers and their agents.
ORG2 AGENTS.md
AGENTS.md instructions for org2AI/ORG2, covering agents.md — agent skill routing for orgii, skill routing table, root-cause-first bug fixing, default delivery flow and ui copy conventions.