MoJoAssistant: Instructions file for Codex

AGENTS.md

MoJoAssistant AGENTS.md is an instructions file for Codex, OpenCode from AvengerMoJo/MoJoAssistant. It costs 634 tokens per session, scanned A, original, MIT.

Repository instructions for MoJoAssistant, covering its source of truth, layered configuration, personal data locations, memory workflow, and Git practices. They tell coding agents where project defaults, personal settings, runtime data, and secrets belong.

In plain words
What is it for?
Use them when changing or operating MoJoAssistant. They guide configuration lookup, memory use, data storage, secret handling, and repository changes.
Why use it?
They reduce the risk of writing personal data into project defaults, exposing secrets, or ignoring required memory and Git procedures. They also establish which files take precedence when settings overlap.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/avengermojo/mojoassistant/agents-md"><img src="https://agentmods.dev/badge/instructions/avengermojo/mojoassistant/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 634 This file is loaded in full into every session.
When invoked 634 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.00634 $0.00634
Opus 5.5 $0.00254 $0.00254
Sonnet 5.5 $0.00127 $0.00127
Haiku 4.5 $0.00063 $0.00063

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

Security

Grade A, and why

MoJoAssistant 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 2mo 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 · 56 lines

How it starts

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

Agent Operating Rules (Global in This Repo)

These rules apply to all coding agents working in this repository.

Source of Truth

  • Primary policy document: Coding Agents Rules.md
  • Agents should follow that file as the canonical rule set.

Configuration and Data Hierarchy

MoJoAssistant follows a Linux-style layered config convention. Agents must respect this:

What Where Rule
System defaults, examples, templates project/config/ Read-only at runtime. Never write here from running code.
Personal config overrides ~/.memory/config/ User's personal layer. Wins over project defaults.
All personal data and runtime state ~/.memory/ Conversations, knowledge, roles, task sessions, events — everything personal.
Secrets and environment .env Never commit. Never hardcode.

Simple rule for agents: when in doubt, ~/.memory/ is home. Read personal state from there. Write personal state there. project/config/ is factory defaults — read for fallback, never write at runtime.

Mandatory Memory Workflow

  1. Use MoJoAssistant MCP memory context to inform decisions before major edits.
  2. Persist important user/assistant exchanges and decisions to memory.
  3. Use memory context to self-correct and improve response quality over time.

Git Workflow

  1. Start work from main by creating a branch named wip_<feature> (or wip_<feature_name>).
  2. Keep implementation work on the wip_<feature> branch until fully tested.
  3. Merge into main only when the user explicitly requests the merge.
  4. All commits must be authored as the user, not as the agent.
  5. The user is accountable for committed code shared with community/company.
  6. Do NOT include Co-Authored-By lines in commit messages. The user is the sole author.

BRIDLE Validation Workflow (Core Principle)

Every state-changing action must prove it worked before moving on:

Act → Validate → Log → Dream → Learn → Correct

Three failure modes to never repeat:

  1. Fail without log — silent failure, same wall next run
  2. Log without learning — dreaming never ingests it, mistake repeats
  3. Mistake without correction — agent self-corrects silently, human never knows

Read the full file on GitHub · 56 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. 2mo ago First seen · 56 lines · 634 tokens per session scan A bba31fb4f014

Subscribe to this mod's changes

MoJoAssistant AGENTS.md is an instructions file published in the GitHub repository AvengerMoJo/MoJoAssistant (42 stars, last pushed 2d ago), licensed MIT. It adds 634 tokens to every session, about $0.0025 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,461 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,750 tokens

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.

denoland/deno · 3,077 tokens