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/wyverncw/monich/agents-mdgit clone --depth 1 https://github.com/WyvernCW/MonichWrote 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/wyverncw/monich/agents-md)<a href="https://agentmods.dev/instructions/wyverncw/monich/agents-md"><img src="https://agentmods.dev/badge/instructions/wyverncw/monich/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.00820 | $0.00820 |
| Opus 5 | $0.00410 | $0.00410 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
Monich 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Skill Registry
This repo contains portable AI coding-agent skills.
When the user asks for scroll-driven landing pages, parallax websites, pinned product showcases, Apple-like product pages, NVIDIA-like reveal pages, or Raycast-like app landing pages, use:
skills/monich/SKILL.md
Scroll Showcase Skill Triggers
Use the Monich skill for requests containing concepts like:
- Raycast-style website
- Apple-style showcase
- NVIDIA-style showcase
- RTX/GPU reveal page
- scroll parallax
- sticky scroll
- pinned reveal
- product storytelling
- premium landing page
- animated SaaS landing page
- app showcase
- AI browser landing page
Required Workflow
- Read
skills/monich/SKILL.md. - Read and recursively scan the whole
templates/folder before choosing references. Do not stop at top-level README files. - If present, scan every folder and file inside
templates/web-template/design-templates/,templates/web-template/horizontal-craft/, andtemplates/web-template/design-systems/. - Read the actual source/reference files inside every template/reference folder, including
.html,.css,.js,.jsx,.tsx,.md,.json, and any design-token files. Do not rely only onSKILL.md,README.md,info.md, or folder names. - Build an inventory of template names, metadata, visual style, page type, layout pattern, motion pattern, component language, color system, typography, and stack.
- Compare the user's request against that inventory and present 2-4 closest template references to the user with a short rationale before implementation when the request is broad or style-sensitive.
- Choose the template or reference set most similar to what the user wants to build.
- Learn from selected references without copying their code line-by-line.
- Generate complete runnable code.
- Include responsive CSS.
- Include reduced-motion fallback.
- Avoid broken imports.
- Avoid copying Raycast, NVIDIA, Apple, or any real brand.
- Match visible copy to the language the user spoke.
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.
- 4d ago First seen · 78 lines · 820 tokens per session scan A 098122fcdd30
Monich AGENTS.md is an instructions file published in the GitHub repository WyvernCW/Monich (3 stars, last pushed 2mo ago), licensed MIT. It adds 820 tokens to every session, about $0.0041 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.