Borrowing it
Nothing to install: this file belongs to Coratch/runwhy. 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/Coratch/runwhy/master/AGENTS.mdgit clone --depth 1 https://github.com/Coratch/runwhyWrote 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/coratch/runwhy/agents-md)<a href="https://agentmods.dev/instructions/coratch/runwhy/agents-md"><img src="https://agentmods.dev/badge/instructions/coratch/runwhy/agents-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/coratch/runwhy/agents-md"><img src="https://agentmods.dev/badge/instructions/coratch/runwhy/agents-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.00270 | $0.00270 |
| Opus 5.5 | $0.00108 | $0.00108 |
| Sonnet 5.5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
runwhy 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 2mo 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
Basic Rules
- Do not write sensitive information anywhere in this project, including API keys, tokens, passwords, private keys, credentials, personal identifiers, or production secrets. Use environment variables, ignored local files, or documented placeholders instead.
- At the end of each conversation turn, read the Obsidian project notes for
agent-session-viewerand maintain a next-action loop:- If there are concrete improvement recommendations from the current user request, repository review, validation results, or competitor/product analysis, treat those recommendations as the primary source for the next execution plan.
- Use the Obsidian notes as project memory and priority context, but do not let stale notes override newer evidence or explicit user direction.
- Present the recommended next execution plan clearly, ask whether the plan should be adjusted, and proceed with execution when the user says no adjustment is needed.
- After completing plan items, update the relevant progress state in Obsidian project notes when appropriate, then provide the next recommended actions.
- Next recommendations may be derived from the user's latest question, newly discovered risks, competitor/product analysis, validation gaps, or the remaining Obsidian roadmap.
- After completing code changes, start the local real RunWhy service for validation. Do not start the demo service unless the user explicitly asks for demo mode.
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.
- 2mo ago First seen · 11 lines · 270 tokens per session scan A 5b9a60c25598
runwhy AGENTS.md is an instructions file published in the GitHub repository Coratch/runwhy (1 stars, last pushed 5mo ago), licensed MIT. It adds 270 tokens to every session, about $0.0011 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.