Borrowing it
Nothing to install: this file belongs to 0xranx/OpenContext. 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/0xranx/OpenContext/main/AGENTS.mdgit clone --depth 1 https://github.com/0xranx/OpenContextWrote 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/0xranx/opencontext/agents-md)<a href="https://agentmods.dev/instructions/0xranx/opencontext/agents-md"><img src="https://agentmods.dev/badge/instructions/0xranx/opencontext/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/0xranx/opencontext/agents-md"><img src="https://agentmods.dev/badge/instructions/0xranx/opencontext/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.01022 | $0.01022 |
| Opus 5.5 | $0.00409 | $0.00409 |
| Sonnet 5.5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
OpenContext 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 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
bin/contains the CLI entry point (oc).src/core/holds the Node.js core logic;src/mcp/hosts the MCP server.src/ui/contains the Vite + React UI, with tests insrc/ui/tests/.src-tauri/andcrates/are the Rust/Tauri desktop and native core layers.tests/includes Node tests by area (core/,search/,native/,integration/).dist/is build output;docs/andREADME*.mdare documentation.
Build, Test, and Development Commands
npm installinstalls dependencies.npm run ui:devstarts the Vite UI dev server;npm run ui:buildbuilds UI assets.npm run tauri:devruns the desktop app;npm run tauri:buildbuilds production binaries.npm run mcpstarts the MCP server;npm run api:devruns the local API server.npm run testruns core/search/native Node tests;npm run test:alladds integration + Rust tests.
Coding Style & Naming Conventions
- Use 2-space indentation for JS/JSON; follow existing formatting in Rust (
cargo fmt). - React components are PascalCase (e.g.,
SearchModal.jsx); modules/files are kebab or camel case as existing. - Git hooks run
cargo fmt --checkviascripts/pre-commit(installed bynpm run prepare).
Testing Guidelines
- Node tests use
node --testand live intests/**orsrc/ui/tests/. - Rust tests live under
crates/opencontext-coreand run withcargo test. - Name tests
*.test.jsor*.test.cjsand keep fixtures near the test if needed.
Commit & Pull Request Guidelines
- Commit messages follow Conventional Commits (e.g.,
feat: ...,fix: ...,chore: ...). - PRs should include a concise description, testing notes (commands run), and UI screenshots/GIFs when UI changes occur.
Configuration Tips
- Desktop builds require Tauri; Windows builds must run on Windows or via CI (
npm run tauri:build:win). - Optional native modules live in
crates/and may require Rust toolchains to build.
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 · 62 lines · 1,022 tokens per session scan A 5285aa964872
OpenContext AGENTS.md is an instructions file published in the GitHub repository 0xranx/OpenContext (1,271 stars, last pushed 4mo ago), licensed MIT. It adds 1,022 tokens to every session, about $0.0041 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.