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.
npx agentmods add agents/szara7678/openakashic/codex-agents-templategit clone --depth 1 https://github.com/szara7678/OpenAkashicWrote 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/agents/szara7678/openakashic/codex-agents-template)<a href="https://agentmods.dev/agents/szara7678/openakashic/codex-agents-template"><img src="https://agentmods.dev/badge/agents/szara7678/openakashic/codex-agents-template.svg" alt="Measured on agentmods" 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.00000 | $0.01297 |
| Opus 5 | $0.00000 | $0.00648 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
Codex AGENTS Template 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summary
Copy this text into ~/.codex/AGENTS.md on each Codex host so every Codex uses the same central Closed Akashic memory.
Template
# Codex Memory Rules
Use Closed Akashic MCP as the only shared long-term working memory.
## Where to read and write
- Browser surface: `https://knowledge.openakashic.com`
- MCP endpoint: `https://knowledge.openakashic.com/mcp/`
- Auth: use the host-level MCP config; prefer a static `Authorization` header on shared local hosts, or `CLOSED_AKASHIC_TOKEN` as the env-var fallback when the token must not be stored in config.
## Operating behavior
1. Before substantial work, search Closed Akashic for related notes, then use validated public knowledge when available.
2. When a project is involved, open `personal_vault/projects/<scope>/<project>/README.md`.
3. Prefer existing notes and update them when they are the right container.
4. After meaningful work, write back one concise, linked note or append one focused section. Distill — never paste raw logs.
5. Keep notes inside `doc/`, organized `personal_vault/` subfolders, or `assets/images/` for uploads.
6. Do not use, clone, or update local `agent-knowledge` as a memory bootstrap.
## Preferred MCP tools
- `search_notes` — Closed Akashic 작업 메모리 검색
- `search_akashic` — Core API 검증 지식 검색 (SLM-ready capsules/claims)
- `read_note`
- `bootstrap_project`
- `path_suggestion`
- `create_folder`
- `rename_folder`
- `move_note`
- `upsert_note`
- `append_note_section`
- `upload_image`
- `debug_recent_requests`
- `debug_log_tail`
## Project folders
- Project index: `personal_vault/projects/<scope>/<project>/README.md`
- Common scopes: `personal`, `company`, `client`, `research`, `ops`
- Agents may create and update project folders through MCP.
- Common starting folders: `architecture/`, `playbooks/`, `incidents/`, `decisions/`, `experiments/`, `reference/`
Reuse
This is deliberately short. Long instructions live in Closed Akashic itself so future changes update one central source instead of many local agent folders.
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.
- 5d ago First seen · 82 lines · 0 tokens per session scan A e3ca35690e7f
Codex AGENTS Template is an agent published in the GitHub repository szara7678/OpenAkashic (3 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,297 tokens. 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-31.
Other agents, from other repositories
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
memory-curator
Audits your memory directory for orphans, phantom references, index drift, broken wiki-links, stale entries, and near-duplicates. Writes a dated health report. Use on-demand (a monthly cadence works well) once your memory store has grown enough that drift between the index and the files is plausible.
brain-os-mode
Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…
t-800-maintainer
Синхронизатор памяти T-800. Use when updating базы знаний T-800, processing UPDATE-QUEUE.md, running docs sync, coverage audit, changelog and install verification. Not for answering beginner questions.
hermes
Nous Research's self-improving agent — persistent memory, autonomous skill creation, runs as a daemon on your own box.
krimto-memory-curator
Periodically reviews team memory in Krimto, identifies stale facts, contradictions, and gaps, and suggests cleanups. Use weekly or before major team decisions to keep memory quality high.