morpheus-ai AGENTS.md

Repository instructions for Morpheus AI, including the required startup, project-connection, editing, compilation, and verification process for AI agents.

In plain words
What is it for?
Use them when preparing an agent, reading project guidance, making roadmap changes, compiling, and running full verification.
Why use it?
They give agents a defined sequence for loading project context and checking changes, including what to do when the local service is unavailable.

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/botagi/morpheus-ai/agents-md
Clone the repo
git clone --depth 1 https://github.com/botAGI/morpheus-ai

Made for: Codex, OpenCode.

Per session 694 This file is loaded in full into every session.
When invoked 694 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.00694 $0.00694
Opus 5 $0.00347 $0.00347
Sonnet 5 $0.00139 $0.00139
Haiku 4.5 $0.00069 $0.00069

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

Security

Grade A, and why

morpheus-ai 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 · 66 lines

How it starts

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

AGENTS.md

Morpheus Bootstrap

Fetch the Morpheus manifest before making changes:

  • Connect manifest: start the API/UI, then fetch /agent/connect?project_root=<PROJECT_ROOT>.
  • One-command prepare: morpheus prepare-agent.
  • Local handoff bundle: morpheus handoff.
  • Local CLI manifest: morpheus agent-connect --json.
  • Local diagnostics: morpheus diagnostics --json.
  • Read WAKE.md before edits.
  • Run compile and verify after meaningful changes.
  • If the API/UI are unavailable, start them with morpheus serve --ui --host 127.0.0.1 --port 8000 --ui-port 5173.
  • Use 0.0.0.0 only for explicit user-approved trusted LAN testing or authenticated proxy environments.

Agent sequence:

  1. Fetch /agent/connect for this project root.
  2. Initialize only when state.initialized is false.
  3. Compile, then read WAKE.md.
  4. Make the requested project change.
  5. Compile again and run morpheus verify --all.

Morpheus Roadmap Autopilot Rule

When asked to continue Morpheus roadmap work:

  • Do one slice only.
  • Prefer tests first.
  • Treat truth-layer work as the data-quality gate, not as a replacement for weights-as-memory.
  • Treat adapter weights as the final memory artifact once dataset quality, eval, activation, and rollback gates exist.
  • Use this roadmap unless the user explicitly changes it:
    • v0.3: semantic classifier as product core.
    • v0.4: dataset quality dashboard.
    • v0.5: adapter memory benchmark.
    • v0.6: agent memory routing.
    • v0.7: team learning loop.
  • No accepted source span means no training example.
  • No eval pass means no adapter activation.
  • No rollback means no production activation.
  • Keep morpheus wake . deterministic by default.
  • Keep cloud providers opt-in.
  • Never make semantic candidates active without review.
  • Never tag, release, publish, or push unless explicitly instructed.
  • Always run:
    • ruff check .
    • pytest tests/ -q
    • morpheus wake . --private
    • morpheus verify --all
  • If touching check, also test file input, stdin input, JSON output, and exit codes.

Read the full file on GitHub · 66 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 · 66 lines · 694 tokens per session scan A 41666179e7c0

Subscribe to this mod's changes

morpheus-ai AGENTS.md is an instructions file published in the GitHub repository botAGI/morpheus-ai (18 stars, last pushed 1mo ago), licensed MIT. It adds 694 tokens to every session, about $0.0035 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.