HoloCore: Instructions file for Codex

AGENTS.md

HoloCore AGENTS.md is an instructions file for Codex, OpenCode from HassanMahomed/HoloCore. It costs 226 tokens per session, scanned C, original, Apache-2.0.

Project instructions for working on HoloCore, including its knowledge systems and project workflow.

In plain words
What is it for?
They are for orienting in HoloCore projects, checking status, researching source files and notes, and making scoped knowledge updates.
Why use it?
They help an agent find relevant project information in the right order and avoid unsupported or duplicate updates.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is HassanMahomed/HoloCore's own configuration. It tells Codex and OpenCode how to work on HoloCore 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 HoloCore configures →

Reuse

Borrowing it

Nothing to install: this file belongs to HassanMahomed/HoloCore. 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/HassanMahomed/HoloCore/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/HassanMahomed/HoloCore

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 HoloCore AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hassanmahomed/holocore/agents-md"><img src="https://agentmods.dev/badge/instructions/hassanmahomed/holocore/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 226 This file is loaded in full into every session.
When invoked 226 The same file — it is already loaded in full.
Security scan C 1 finding. 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.00226 $0.00226
Opus 5 $0.00113 $0.00113
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00023 $0.00023

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

Security

Grade C, and why

HoloCore AGENTS.md scanned grade C with 1 finding 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 8d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- holocore:project-instructions -->
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

AGENTS.md · 11 lines

What it actually says

HoloCore knowledge workflow

Run holocore status before broad orientation. For project work, use a fresh Atlas first to identify relevant files and relationships, search corresponding Archive notes second, query Animus third only when prior work or chats matter, and open exact source files last. Build one route plan and execute it once; never route a HoloCore search back into itself. Each subsystem may run at most once per request. Writes must be explicit and scoped. Promote only verified durable knowledge into Archive, update existing notes before creating duplicates, and record uncertain claims as questions rather than facts.

Archive = verified knowledge. Atlas = structural map. Animus = remembered history. World = project. Sector = area inside a project. Memory Shard = raw remembered fragment. Archive Entry = polished durable note. Signal = one mapped thing. Constellation = group of related mapped things.

HoloCore project context

Read HOLOCORE.md before project-context work. Use HoloCore's check-first route and never loop a result back into HoloCore.

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. 8d ago First seen · 11 lines · 226 tokens per session scan C 2db955cf6a0d

Subscribe to this mod's changes

HoloCore AGENTS.md is an instructions file published in the GitHub repository HassanMahomed/HoloCore (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 226 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens