Borrowing it
Nothing to install: this file belongs to malwarebo/nyrve. 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/malwarebo/nyrve/main/.github/instructions/oss.instructions.mdgit clone --depth 1 https://github.com/malwarebo/nyrveWrote 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/malwarebo/nyrve/oss)<a href="https://agentmods.dev/instructions/malwarebo/nyrve/oss"><img src="https://agentmods.dev/badge/instructions/malwarebo/nyrve/oss/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/malwarebo/nyrve/oss"><img src="https://agentmods.dev/badge/instructions/malwarebo/nyrve/oss.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.00286 | $0.00286 |
| Opus 5.5 | $0.00114 | $0.00114 |
| Sonnet 5.5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
nyrve oss.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 1mo 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.
This is a copy
100% identical to vscode oss.instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
OSS License Review
When reviewing changes to these files, verify:
ThirdPartyNotices.txt
- Every new entry has a license type header (e.g., "MIT License", "Apache License 2.0")
- License text is present and non-empty for every entry
- License text matches the declared license type (e.g., MIT-declared entry actually contains MIT license text, not Apache)
- Removed entries are cleanly removed (no leftover fragments)
- Entries are sorted alphabetically by package name
cglicenses.json
- New overrides have a justification comment
- No obviously stale entries for packages no longer in the dependency tree
cgmanifest.json
- Package versions match what's actually installed
- Repository URLs are valid and point to real source repositories
- Newly added license identifiers should use SPDX format where possible
- License identifiers match the corresponding ThirdPartyNotices.txt entries
Red Flags
- Any newly added copyleft license (GPL, LGPL, AGPL) — flag immediately (existing copyleft entries like ffmpeg are pre-approved)
- Any "UNKNOWN" or placeholder license text
- License text that appears truncated or corrupted
- A package declared as MIT but with Apache/BSD/other license text (or vice versa)
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.
- 1mo ago First seen · 35 lines · 286 tokens per session scan A fe4dfb436f27
nyrve oss.instructions.md is an instructions file published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 4mo ago), licensed MIT. It adds 286 tokens to every session, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vscode oss.instructions.md, differing in 0 lines, and is treated as a copy.
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.