What is mcp-server CLAUDE.md?

A set of instructions for agents working on Omniology's MCP server and ElizaOS plugin repositories. It defines which repositories and documentation areas are in scope, and which changes are forbidden.

Use it to guide documentation, examples, tests, release preparation, pull requests, and package metadata work in the specified Omniology repositories.

It prevents agents from making unapproved changes, such as editing the engine, changing secrets, pushing directly to the main branch, or altering core behavior without approval.

How omniologynow-rgb/mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to omniologynow-rgb/mcp-server. 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/omniologynow-rgb/mcp-server/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/omniologynow-rgb/mcp-server

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/omniologynow-rgb/mcp-server/claude-md/github.svg)](https://agentmods.dev/instructions/omniologynow-rgb/mcp-server/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/omniologynow-rgb/mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/omniologynow-rgb/mcp-server/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/omniologynow-rgb/mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/omniologynow-rgb/mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 605 This file is loaded in full into every session.

When invoked 605 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.

Model	Per session	Once invoked
Fable 5.1	$0.00605	$0.00605
Opus 5.5	$0.00242	$0.00242
Sonnet 5.5	$0.00121	$0.00121
Haiku 4.5	$0.00060	$0.00060

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

Security

Grade A, and why

mcp-server CLAUDE.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.

CLAUDE.md · 55 lines

How it starts

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

Omniology Repo Access — Agent Working Guidelines (v1)

Repos in scope

@omniology/mcp-server (npm STDIO package)
@omniology/eliza-plugin (native ElizaOS plugin)

Agent's ROLE

Ship user-facing polish + docs + release hygiene in the above two repos ONLY.

Focus areas: README quality, README badges, npm package metadata, examples/quickstarts, changelog, GitHub topics, social-preview images.

Agent MAY

✓ Open PRs against feature branches (never push to main directly)
✓ Update README, CHANGELOG, examples, docs
✓ Add tests + verify existing test suite passes
✓ Bump package versions per semver
✓ Publish to npm ONLY after Matt approves the PR + reviews the release notes
✓ Ask questions via GitHub issues if unclear

Agent MUST NOT

✗ Touch the engine repo (omniology/omniology-engine)
✗ Touch the website repo (Emergent-managed)
✗ Push to main directly on ANY repo
✗ Modify anything under a .env* file, Fly secrets, or GitHub Actions secrets
✗ Merge its own PRs (Matt merges after review)
✗ Change core behavior of MCP tools without design approval
✗ Modify the on-chain program interaction layer (register_agent message body, submit_entry signing flow, delegate references)
✗ Add or remove dependencies without a stated reason in the PR
✗ Publish npm packages without Matt's explicit "publish" approval per version

Every PR must include (in the description)

What changed — 1-3 bullets
Why — user-visible benefit or bug fixed
Files touched — full paths list
Test evidence — one of: screenshot of local npm test passing / CI check green / manual test steps run
Backwards compatibility — any breaking change? if yes flag it
Version bump — patch/minor/major + reason
Dependencies added/removed — none by default; if yes, why
Ready to publish? — yes/no; if yes, waiting on Matt's go

Coordination protocol

Work only in the 2 repos listed above.
If a change to the engine or website seems needed, write a GitHub issue in that repo and flag it in the handoff. Do NOT touch the other repo.
Matt is the sole merge/publish/release approver.

Read the full file on GitHub · 55 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.

2mo ago First seen · 55 lines · 605 tokens per session scan A 14b4d95ade7b

Subscribe to this mod's changes

mcp-server CLAUDE.md is an instructions file published in the GitHub repository omniologynow-rgb/mcp-server (1 stars, last pushed 3mo ago), licensed MIT. It adds 605 tokens to every session, about $0.0024 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-31.

mcp-server CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp-server CLAUDE.mdomniologynow-rgb/mcp-server	Instructions file	1	3mo ago	MIT	A	605	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

mcp-server: Instructions file for Claude Code