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/moonchanyong/megaman/agents-mdgit clone --depth 1 https://github.com/moonchanyong/megamanWrote 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/moonchanyong/megaman/agents-md)<a href="https://agentmods.dev/instructions/moonchanyong/megaman/agents-md"><img src="https://agentmods.dev/badge/instructions/moonchanyong/megaman/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 | $0.00319 | $0.00319 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
megaman 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 5d 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
AGENTS.md
This repository exists to design and implement the megaman CLI.
megaman is not just a tool for swapping rule files for coding agents. It is intended to switch the default context of the primary agent based on the job at hand. The key idea is not only changing internal subagents, but changing the main agent's default purpose, response priorities, behavior, and the set of rules, skills, and configuration it should operate with.
Product Summary
- Name:
megaman - One-line description: CLI for switching the primary context of coding agents.
- Onboarding:
npx megaman init
Product Direction
- Do not design this as a simple rule switcher.
- Prefer a structure built from a thin shared core plus purpose-specific layers.
- Optimize for changing the behavior of the primary agent in a way the user can actually feel.
- Tool-specific rule files, skills, and config files can be generated or synced as outputs when needed.
- Assume that
megamanmust be built as an agent-friendly CLI and that its interface should follow the specification indocs/agent-friendly-cli.md.
Reference
- Treat docs/agent-friendly-cli.md as a required implementation constraint for this CLI.
- Treat docs/DESIGN.md as the current product design and implementation baseline.
- Treat README.md as the user-facing install and quick start entry point.
- Read both documents before making implementation or design decisions.
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.
- 5d ago First seen · 27 lines · 319 tokens per session scan A fff10c7553e7
megaman AGENTS.md is an instructions file published in the GitHub repository moonchanyong/megaman (4 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 319 tokens to every session, about $0.0016 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).
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.
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).