Borrowing it
Nothing to install: this file belongs to nagisanzenin/omniplugin. 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/nagisanzenin/omniplugin/main/CLAUDE.mdgit clone --depth 1 https://github.com/nagisanzenin/omnipluginWrote 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/nagisanzenin/omniplugin/claude-md)<a href="https://agentmods.dev/instructions/nagisanzenin/omniplugin/claude-md"><img src="https://agentmods.dev/badge/instructions/nagisanzenin/omniplugin/claude-md.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.00699 | $0.00699 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
omniplugin 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 8d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
omniplugin — agent instructions
This repo is a playbook that ships as a plugin: distilled guidance for building and maintaining omni-platform agent plugins, plus skills/omniplugin/SKILL.md (the installable router — Claude Code / Codex / Antigravity manifests are in .claude-plugin/, .codex-plugin/, root plugin.json; one repo, one shared core, native installs on many agentic platforms). The reference implementation behind every claim is https://github.com/nagisanzenin/engram — when this playbook and reality disagree, check engram's current main, then fix the playbook.
Route by task
| You were asked to… | Read, in order |
|---|---|
| Create a new omni-platform plugin | docs/01-anatomy.md → docs/02-portability-rules.md, then the platform files for your launch targets. Copy templates/session-hook.sh patterns from day one — retrofitting portability is the expensive way. |
| Add a platform to an existing plugin | docs/03-adding-a-platform.md (the checklist) + docs/platforms/<target>.md if it exists, else start from templates/platform-intake.md. Do Phase 1 research from primary sources even when a crib sheet exists — check its date first. |
| Release / maintain across platforms | docs/04-maintenance.md; engram's RELEASE_PROTOCOL.md is the full reference implementation. |
| Debug a platform integration | docs/05-pitfalls.md (it's probably in there) + the platform crib sheet. |
| Evaluate a new/unknown platform | docs/platforms/landscape.md for the survey + templates/platform-intake.md for the questions. |
Non-negotiables when applying this playbook
- Research the target platform's actual loader from primary sources before writing glue (schema, CLI changelog, flagship plugin). Never port by analogy.
- Check every new root-level path against every shipped platform's discovery conventions (namespace bleed — pitfall #2).
- Hooks: self-resolving, silent-unless-useful, degrade to silence, fail closed,
exit 0. - Ship honest status: Verified (with the platform version) vs Not-verified (with why it's harmless), in every install doc.
- The shared core stays byte-identical across platforms. Platform differences live in glue, waterfalls, and install docs — never as forks of core files.
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.
- 8d ago First seen · 29 lines · 699 tokens per session scan A 0750c5492df0
omniplugin CLAUDE.md is an instructions file published in the GitHub repository nagisanzenin/omniplugin (5 stars, last pushed 12d ago), licensed MIT. It adds 699 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-31.
Other instructions, from other repositories
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).
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).
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.
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.