OpenContext AGENTS.md

Repository guidance for OpenContext, a desktop application with a Node.js core, a React web interface, an MCP server, and Rust/Tauri native components. Tauri is a framework for packaging web interfaces as desktop apps.

In plain words
What is it for?
Use it when working on the command-line tool, search and core logic, React interface, local API, MCP server, desktop shell, or Rust code.
Why use it?
It explains where each part of the application lives and which commands build, run, and test the different layers.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/0xranx/opencontext/agents-md
Clone the repo
git clone --depth 1 https://github.com/0xranx/OpenContext

Made for: Codex, OpenCode.

Per session 1,022 This file is loaded in full into every session.
When invoked 1,022 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01022 $0.01022
Opus 5 $0.00511 $0.00511
Sonnet 5 $0.00204 $0.00204
Haiku 4.5 $0.00102 $0.00102

Measured 2d ago against content hash 5285aa964872, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

AGENTS.md · 62 lines

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 in src/ui/tests/.
  • src-tauri/ and crates/ are the Rust/Tauri desktop and native core layers.
  • tests/ includes Node tests by area (core/, search/, native/, integration/).
  • dist/ is build output; docs/ and README*.md are documentation.

Build, Test, and Development Commands

  • npm install installs dependencies.
  • npm run ui:dev starts the Vite UI dev server; npm run ui:build builds UI assets.
  • npm run tauri:dev runs the desktop app; npm run tauri:build builds production binaries.
  • npm run mcp starts the MCP server; npm run api:dev runs the local API server.
  • npm run test runs core/search/native Node tests; npm run test:all adds 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 --check via scripts/pre-commit (installed by npm run prepare).

Testing Guidelines

  • Node tests use node --test and live in tests/** or src/ui/tests/.
  • Rust tests live under crates/opencontext-core and run with cargo test.
  • Name tests *.test.js or *.test.cjs and 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.

Read the full file on GitHub · 62 lines

Changes

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.

  1. 2d ago First seen · 62 lines · 1,022 tokens per session scan A 5285aa964872

Subscribe to this mod's changes

OpenContext AGENTS.md is an instructions file published in the GitHub repository 0xranx/OpenContext (756 stars, last pushed 2mo ago), licensed MIT. It adds 1,022 tokens to every session, about $0.0051 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.