Borrowing it
Nothing to install: this file belongs to sfc-gh-myoung/ai_coding_rules. 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/sfc-gh-myoung/ai_coding_rules/main/AGENTS.mdgit clone --depth 1 https://github.com/sfc-gh-myoung/ai_coding_rulesWrote 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/sfc-gh-myoung/ai_coding_rules/agents-md)<a href="https://agentmods.dev/instructions/sfc-gh-myoung/ai_coding_rules/agents-md"><img src="https://agentmods.dev/badge/instructions/sfc-gh-myoung/ai_coding_rules/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/sfc-gh-myoung/ai_coding_rules/agents-md"><img src="https://agentmods.dev/badge/instructions/sfc-gh-myoung/ai_coding_rules/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.00711 | $0.00711 |
| Opus 5.5 | $0.00284 | $0.00284 |
| Sonnet 5.5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
ai_coding_rules 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Conventions for the root Makefile. Reference: docs/USING_DEV_CLI.md.
Help annotations
make help is generated by awk from the Makefile itself. No Python or other script.
| Annotation | Effect |
|---|---|
## @section Name | note |
Starts a help section with an optional dim note |
## @quickstart cmd | text |
Row in the Quickstart block |
## @example cmd | text |
Row in the closing Examples block |
## @override VAR=value | text |
Row in the Overrides block |
## @inputs VAR=x [OPT=y] |
Inputs of the next target (yellow) |
## @needs tools or cost |
Prerequisites of the next target (tools, credentials, AI credits) |
target: ## description |
Lists the target; keep it to one short line |
Put @inputs/@needs on the line directly above the target. Put the required inputs there, not in the description.
Color and TTY rules
- Bold sections, cyan targets, yellow inputs, dim notes, green ok, red errors.
- Color is on only when the stream is a TTY and
TERMis notdumb, or whenFORCE_COLOR/CLICOLOR_FORCEis set.NO_COLORalways wins. Piped output has no escape codes. - Use
$(call say,text,G),$(call fail,text)and$(call colors,fd)in recipes.$(error)messages (therequiremacro) are colored from stderr at parse time. Message arguments must not contain commas.
Macros and flags
require:$(call require,VAR,usage)stops when a variable is empty.need:$(call need,tool,message)stops with an install message.shq:$(call shq,value)single-quotes a value for the shell. Quote every user-supplied value.- Recipes are silent (
.SILENT);V=1orVERBOSE=1echoes commands. DRY_RUN=1previews release steps;FORCE=1skips cleanup prompts.- Recursion uses
$(MAKE) $(SUBMAKE) target(keepsmake -C/-fworking). Write$(MAKE)literally:make -nonly recurses into lines that contain it. Release recipes must never contain$(MAKE).
Hygiene checklist
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 · 41 lines · 711 tokens per session scan A 5f27517bee8c
ai_coding_rules AGENTS.md is an instructions file published in the GitHub repository sfc-gh-myoung/ai_coding_rules (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 711 tokens to every session, about $0.0028 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-10-26.
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.