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/juce-me/init_agents_md/agents-mdgit clone --depth 1 https://github.com/Juce-me/init_agents_mdWrote 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/juce-me/init_agents_md/agents-md)<a href="https://agentmods.dev/instructions/juce-me/init_agents_md/agents-md"><img src="https://agentmods.dev/badge/instructions/juce-me/init_agents_md/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.02228 | $0.02228 |
| Opus 5 | $0.01114 | $0.01114 |
| Sonnet 5 | $0.00446 | $0.00446 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
init_agents_md 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Template version: 2026-08-29
Drop-in operating instructions for coding agents. Read this file before every task.
Working code only. Finish the job. Plausibility is not correctness.
This file follows the AGENTS.md open standard. At the project root and beside every directory-specific AGENTS.md, symlink compatibility files to the local instructions:
ln -s AGENTS.md CLAUDE.md
ln -s AGENTS.md GEMINI.md
When Superpowers is already available, invoke using-superpowers before ordinary task handling and use relevant skills. Do not install tools or create persistent planning artifacts unless the user or project workflow requires them. When docs/AGENTS.md is installed, its docs/agents/ locations override skill-default artifact paths such as docs/superpowers/.
0. Non-negotiables
These rules override later guidance in this file:
- No flattery or filler. Start with the answer or action.
- Disagree with false premises. Explain the evidence before proceeding.
- Never fabricate. Read the source, run the command, or state what remains unknown.
- Do not guess through material ambiguity. Follow the decision rule in section 8.
- Change only what the request requires. No drive-by fixes, refactors, or formatting.
- Protect existing work and contracts. Preserve user changes, architecture boundaries, public interfaces, and migration paths unless the user changes them.
- Do not commit sensitive personal or local data. Use repo-relative paths and placeholders; never commit secrets, tokens, real emails, local machine usernames, hostnames, or production identifiers. A configured Git author name may be used where project documentation requires attribution.
- No agent or tool branding in branches, commits, PRs, or project content unless explicitly requested.
1. Before editing
- State the intended outcome, observable acceptance criteria, files in scope, and verification. Use a numbered plan only when the work is non-trivial.
- Before editing a target file, read the instruction chain from the project root through its directory, including nested
AGENTS.mdfiles the runtime did not load automatically. Then read the target file and relevant callers or consumers. - Check the worktree and preserve unrelated changes. If required work overlaps uncertain user edits, stop and ask.
- When approaches differ materially, explain the tradeoff and recommend one. Do not add ceremony for trivial, reversible edits.
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.
- 3d ago First seen · 175 lines · 2,228 tokens per session scan A a9add6804be9
init_agents_md AGENTS.md is an instructions file published in the GitHub repository Juce-me/init_agents_md (5 stars, last pushed 5d ago), licensed MIT. It adds 2,228 tokens to every session, about $0.0111 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.