remnic: Instructions file for Codex

AGENTS.md

remnic AGENTS.md is an instructions file for Codex, OpenCode from joshuaswarren/remnic. It costs 21,161 tokens per session, scanned A, original, MIT.

A guide for contributors to Remnic, an open-source memory system that stores and retrieves information for different platforms.

In plain words
What is it for?
Use it when implementing adapters, changing core, server, or command-line behavior, or preparing public commits, issues, and pull requests.
Why use it?
It explains the project’s boundaries and privacy rules, helping contributors avoid putting platform-specific code in the core or exposing private details in public work.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is joshuaswarren/remnic's own configuration. It tells Codex and OpenCode how to work on remnic itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything remnic configures →

Reuse

Borrowing it

Nothing to install: this file belongs to joshuaswarren/remnic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/joshuaswarren/remnic/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/joshuaswarren/remnic

Made for: Codex, OpenCode.

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

agentmods badge for remnic AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/joshuaswarren/remnic/agents-md/github.svg)](https://agentmods.dev/instructions/joshuaswarren/remnic/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/joshuaswarren/remnic/agents-md"><img src="https://agentmods.dev/badge/instructions/joshuaswarren/remnic/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.

agentmods 80×15 button for remnic AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/joshuaswarren/remnic/agents-md"><img src="https://agentmods.dev/badge/instructions/joshuaswarren/remnic/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21,161 This file is loaded in full into every session.
When invoked 21,161 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.21161 $0.21161
Opus 5.5 $0.08464 $0.08464
Sonnet 5.5 $0.04232 $0.04232
Haiku 4.5 $0.02116 $0.02116

Measured 2d ago against content hash ce792bca07df, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

remnic 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 · 1,691 lines

How it starts

The opening of the file, as written. The whole thing — 1,691 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Remnic - Agent Guide

PUBLIC, OPEN-SOURCE REPOSITORY. Remnic is a public open-source project. Everything pushed to GitHub — commits, issues, PRs, review comments — is world-readable. Never include PII or operator-specific infrastructure details (hostnames, internal IPs, usernames/home paths, client or project names, memory IDs or memory content, links to private repos/docs). Write issues and PRs for the general case: describe the reproducing deployment shape and design fixes that benefit all users, not one operator's setup. Full rules: "PUBLIC REPOSITORY — Privacy Policy" below.

Architecture Boundaries (Non-Negotiable)

Remnic is a multi-platform memory system. Keep these boundaries intact on every change:

  1. @remnic/core, @remnic/server, and @remnic/cli own Remnic's core behavior. Core memory semantics, storage, retrieval, extraction, governance, and standalone operation must live there.
  2. Core and standalone paths must not depend on OpenClaw, Hermes, or any future host. Host integrations may consume core. Core must not reach back into host SDKs, config shapes, or runtime lifecycles.
  3. Platform-specific behavior belongs in platform adapters only. OpenClaw-specific code belongs in packages/plugin-openclaw plus the current root src/ compatibility wiring that still hosts OpenClaw runtime entrypoints today. Hermes-specific code belongs in packages/plugin-hermes. Keep host logic thin and translation-focused.
  4. Do not reinvent host-native features. If OpenClaw, Hermes, or another platform already provides a runtime capability, plugin hook, command surface, or extension primitive, use that real upstream contract instead of recreating a parallel Remnic abstraction.
  5. Verify host behavior against current upstream source and docs before implementing it. Issue text, old local docs, or remembered APIs are not enough for host-facing work.
  6. Desktop-capture subsystems obey the same split: packages/remnic-core/src/activity/ and packages/remnic-core/src/meetings/ are host-agnostic core subsystems, while the capture packages (@remnic/capture-audio, @remnic/capture-screen) and the meeting/wearable connectors (@remnic/connector-*) are optional adapters that consume core and never the reverse (umbrella #1896).

Read the full file on GitHub · 1,691 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 Changed · +2 lines · +37 tokens per session ce792bca07df
  2. 13d ago Changed · +247 tokens per session 25ab5c579eb3
  3. 14d ago Changed · +6 lines · +72 tokens per session 058f9e82f932
  4. 18d ago Changed · -812 lines · -10,763 tokens per session 11f78ecd3129
  5. 1mo ago Changed · +2 lines · +115 tokens per session 93d27569dccf
  6. 1mo ago Changed · +12 tokens per session c6a48c6ed5a9
  7. 1mo ago First seen · 2,493 lines · 31,441 tokens per session scan A 9a36aced9bb3

Subscribe to this mod's changes

remnic AGENTS.md is an instructions file published in the GitHub repository joshuaswarren/remnic (229 stars, last pushed today), licensed MIT. It adds 21,161 tokens to every session, about $0.0846 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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens