Borrowing it
Nothing to install: this file belongs to CodeSeoul/automate-development-with-agents. 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/CodeSeoul/automate-development-with-agents/main/AGENTS.mdgit clone --depth 1 https://github.com/CodeSeoul/automate-development-with-agentsWrote 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/codeseoul/automate-development-with-agents/agents-md)<a href="https://agentmods.dev/instructions/codeseoul/automate-development-with-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/codeseoul/automate-development-with-agents/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/codeseoul/automate-development-with-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/codeseoul/automate-development-with-agents/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.00724 | $0.00724 |
| Opus 5.5 | $0.00290 | $0.00290 |
| Sonnet 5.5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
automate-development-with-agents 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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for any AI agent working in this repository. Keep this file short and precise — every line should change agent behavior. If a line wouldn't cause a mistake when removed, delete it.
Working principles
- Understand before changing. Read the relevant code and existing patterns before editing. Match the conventions already in the file you're touching.
- Smallest change that works. Don't refactor, rename, or reformat code you weren't asked to touch. Keep diffs focused on the task.
- Verify your work. Run the relevant build, tests, and linter before claiming a task is done. Report failures honestly with the actual output — never assert success you didn't confirm.
- Ask when genuinely blocked. If requirements are ambiguous in a way that changes the outcome, ask. Otherwise pick the sensible default and state the assumption.
Conventions
- Follow the language and formatting already used in each file (indentation, quotes, naming). When in doubt, copy the nearest existing example.
- Comments explain why, not what. Match the surrounding comment density — don't add narration to self-explanatory code.
- Keep functions small and named for what they do. Prefer clarity over cleverness.
Prohibitions (each paired with what to do instead)
- Don't use an agent to do a linter's job. Run the project's formatter/linter rather than hand-fixing style.
- Don't commit secrets or credentials. Read config from environment variables; add new
secrets to
.gitignore-d files only. - Don't commit or push unless asked. Make the change, verify it, and let the user
review. When asked to commit, never use
--no-verify— fix what the hooks flag. - Don't leave dead code or commented-out blocks. Delete what you replace; git history preserves it.
- Don't suppress errors to make output clean. Surface the failure and fix the cause.
Project artifacts
This file holds always-apply invariants. Three directories hold per-change artifacts, each with its own lane:
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.
- 1mo ago First seen · 70 lines · 724 tokens per session scan A c87fb2505642
automate-development-with-agents AGENTS.md is an instructions file published in the GitHub repository CodeSeoul/automate-development-with-agents (5 stars, last pushed 5mo ago), licensed MIT. It adds 724 tokens to every session, about $0.0029 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.