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.
npx agentmods add instructions/waynejin0918/omni-rewriter/agents-mdgit clone --depth 1 https://github.com/WayneJin0918/Omni-RewriterWrote 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/waynejin0918/omni-rewriter/agents-md)<a href="https://agentmods.dev/instructions/waynejin0918/omni-rewriter/agents-md"><img src="https://agentmods.dev/badge/instructions/waynejin0918/omni-rewriter/agents-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.00141 | $0.00141 |
| Opus 5 | $0.00071 | $0.00071 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
Omni-Rewriter 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 6d 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.
What it actually says
Agent notes
Maintainer and coding-agent conventions live in docs/AGENTS.md.
Also see .cursor/skills/omni-rewriter-h3-pe/SKILL.md,
.cursor/skills/omni-rewriter-model-contribution/SKILL.md,
and .cursor/skills/omni-rewriter-promo-pipeline/SKILL.md
for promo film assemble workflows.
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.
- 6d ago First seen · 8 lines · 141 tokens per session scan A 95aaaa14b819
Omni-Rewriter AGENTS.md is an instructions file published in the GitHub repository WayneJin0918/Omni-Rewriter (84 stars, last pushed 16d ago), licensed Apache-2.0. It adds 141 tokens to every session, about $0.0007 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.
Other instructions, from other repositories
minimax-h3-opencode-skills AGENTS.md
Instructions for unknowlei/minimax-h3-opencode-skills, covering ai installation contract, install target, required installation and safety.
DataDesigner CLAUDE.md
Claude Code instructions for NVIDIA-NeMo/DataDesigner, a project described as: 🎨 NeMo Data Designer: Generate high-quality synthetic data from scratch or from seed data.
ANWS AGENTS.md
Instructions for Haaaiawd/ANWS, covering agents.md - ai 协作协议, 🧠 30秒恢复协议 (quick recovery), 🗺️ 地图 (领地感知), 🛠️ 工作流注册表 and 📜 宪法 (the constitution).
TLDR CLAUDE.md
Instructions for 0p9b/TLDR, covering claude.md — tldr maintainer guide, product, source layout, edit rules and install paths.
TLDR AGENTS.md
Instructions for 0p9b/TLDR: @./skills/tldr/SKILL.md @./skills/tldr-commit/SKILL.md @./skills/tldr-review/SKILL.md @./skills/tldr-compress/SKILL.md.
nano-banana-image-skill AGENTS.md
Instructions for Emily2040/nano-banana-image-skill, covering nano banana image skill — agents instructions, canonical entrypoint, secondary files, working agreements and expected outputs.