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/florian101010/awesome-agentic-ai-coding-template/docsgit clone --depth 1 https://github.com/florian101010/awesome-agentic-AI-coding-templateWrote 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/florian101010/awesome-agentic-ai-coding-template/docs)<a href="https://agentmods.dev/instructions/florian101010/awesome-agentic-ai-coding-template/docs"><img src="https://agentmods.dev/badge/instructions/florian101010/awesome-agentic-ai-coding-template/docs.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.00320 | $0.00320 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
Documentation Rules 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.
What it actually says
Documentation Instructions
Purpose
Use these rules when editing files under docs/ to keep documentation drift-free and aligned with implementation.
Core Rules
- Treat code/config as source of truth; update docs to match code, never vice versa without explicit requirement.
- Keep wording concise, factual, and implementation-aligned.
- Preserve existing document structure unless a structural change is explicitly needed.
Mandatory Sync Targets
When behavior, architecture, or schema changes, update all affected files:
docs/README.mddocs/ARCHITECTURE.mddocs/CHANGELOG.md- [FILL: Add further doc paths relevant to your project]
docs/decisions/(if architectural — create/update ADR file)
Data Accuracy Checks
Before finalizing documentation changes:
- Verify any count or metric values against the actual source (config files, code).
- Ensure no leading
/or./paths are introduced (if the project uses relative paths).
Process
- Follow
.agent/workflows/doc-audit.mdfor full drift audits. - Keep release-relevant updates reflected in
CHANGELOG.md. - For architecture-level changes, ensure an ADR file exists in
decisions/. - Run
.githooks/pre-commitbefore final handoff.
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 · 45 lines · 320 tokens per session scan A cd3c5427a8b2
Documentation Rules is an instructions file published in the GitHub repository florian101010/awesome-agentic-AI-coding-template (4 stars, last pushed 6mo ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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
agent-skills AGENTS.md
AGENTS.md instructions for helderberto/agent-skills, covering agents.md, repository overview, project structure, integration model and opencode integration.
aiworkspace AGENTS.md
Instructions for a-tokyo/aiworkspace, covering ai workspace, structure, key commands, conventions and code quality.
ai-workspace-archive copilot-instructions.md
Copilot instructions for HIDORAKAI002/ai-workspace-archive, covering github copilot instructions for autogpt, repository overview, build and validation instructions, essential setup commands and runtime requirements.
P0G AGENTS.md
Instructions for yz9yt/P0G, covering p0g agent guidelines, core principles, 1. clean instance mindset, 2. explicit over implicit and 3. minimal footprint.
cc-use-exp field-mapping-safety.instructions.md
Instructions for doccker/cc-use-exp, covering 字段映射安全规范, 触发场景, 5 个核心陷阱速记, 同步覆盖决策矩阵（陷阱 #5） and 必检清单.
cc-use-exp general.instructions.md
Instructions for doccker/cc-use-exp, a project described as: ⛔ No longer maintained → dev-agent-kit/recipes 让 Claude Code、Antigravity、Gemini CLI、Codex、Cursor 开箱即用的分层配置模板，总结十多年的日常开发经验.