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.
curl -O https://raw.githubusercontent.com/omniologynow-rgb/mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/omniologynow-rgb/mcp-serverWrote 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/instructions/omniologynow-rgb/mcp-server/claude-md)<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.
<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>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 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
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 12d 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 — 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.
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.
- 12d ago First seen · 55 lines · 605 tokens per session scan A 14b4d95ade7b
mcp-server CLAUDE.md is an instructions file published in the GitHub repository omniologynow-rgb/mcp-server (1 stars, last pushed 1mo ago), licensed MIT. It adds 605 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
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.
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.
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.
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).
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.
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).