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/snowdreamtech/template/rulesgit clone --depth 1 https://github.com/snowdreamtech/templateWhat 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.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
template rules.instructions.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 today.
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 โ 40 lines โ stays where its author put it; the contents beside it link to each section on GitHub.
๐จ CRITICAL SYSTEM INSTRUCTION ๐จ
Before answering ANY prompt or executing ANY code in this repository, you MUST first read and strictly adhere to ALL the rules defined in the following directory:
Step 1: Read ALL Core Rule Files
๐ .agent/rules/ โ Read in numerical order:
.agent/rules/01-general.mdโ Language, communication, idempotency, cross-platform, network, security & audit.agent/rules/02-coding-style.mdโ Commit messages, code quality, error handling, documentation, naming conventions.agent/rules/03-architecture.mdโ Project structure, AI IDE integration, design principles.agent/rules/04-security.mdโ Credentials, access control, encryption, scanning, incident response.agent/rules/05-dependencies.mdโ Locking, integrity, auditing, release process, changelog.agent/rules/06-ci-testing.mdโ Test types, CI pipeline, test data, fast feedback, quality gates.agent/rules/07-git.mdโ Commits, branching, pull requests, code review, history hygiene.agent/rules/08-dev-env.mdโ Environment consistency, dev container, scripts, pre-commit hooks, debugging.agent/rules/09-ai-interaction.mdโ Safety boundaries, code generation, communication, context handling, quality.agent/rules/10-ui-ux.mdโ Styling, componentization, accessibility, performance, i18n (frontend projects only).agent/rules/11-deployment.mdโ Containerization, secrets, deployment pipeline, IaC, observability & DR
Step 2: Read Relevant Language & Framework Rule Files
After reading the core rules, inspect the project's file structure and configuration files to identify the languages and frameworks in use. Then read the corresponding rule files from .agent/rules/.
Why This File Exists
This project uses a unified rule system to ensure consistent AI behavior
across all AI-powered IDEs and tools (Cursor, Windsurf, GitHub Copilot,
Cline, Claude, Gemini, Trae, Roo Code, Augment, Amazon Q, Kiro,
Continue, Junie, etc.). This file is a redirect entry point โ
the actual rules live in .agent/rules/ as the Single Source of Truth.
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.
- today First seen ยท 40 lines ยท 543 tokens per session scan A 45f7f745953f
template rules.instructions.md is an instructions file published in the GitHub repository snowdreamtech/template (15 stars, last pushed yesterday), licensed MIT. It adds 543 tokens to every session, about $0.0027 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-09-01.
Other instructions, from other repositories
langgraph AGENTS.md
Instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
cookiecutter-mlops-package AGENTS.md
Instructions for fmind/cookiecutter-mlops-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.
nuxt-supabase-starter CLAUDE.md
Instructions for YuDefine/nuxt-supabase-starter, covering claude.md, language, project structure and meta vs template ้็.
spacebot AGENTS.md
AGENTS.md instructions for spacedriveapp/spacebot, covering agents.md, what spacebot is, javascript tooling (critical), migration safety and delivery gates (mandatory).
rust-2026-template AGENTS.md
Instructions for d-oit/rust-2026-template, covering agent coding contract, quick reference, project structure, agent skills (.agents/skills/) and multi-agent support.
cuga-agent AGENTS.md
AGENTS.md instructions for cuga-project/cuga-agent, covering agent guidelines, mark tests with their type, ci discovers tests by directory โ do not edit workflow yaml, lazy imports โ rules for new code and tests and cuga/init.py โ pep 562 lazy exports.