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/azacdev/knowledge-agent-template/agents-mdgit clone --depth 1 https://github.com/azacdev/knowledge-agent-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.00553 | $0.00553 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
knowledge-agent-template 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 yesterday.
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eve Agent App
This project uses the eve framework. Before writing code, read the relevant guide
from the installed eve package docs. In most installs, those docs are at
node_modules/eve/docs/. In workspaces or local package installs, resolve the
installed eve package location first and read its docs/ directory. If
package docs are unavailable, use https://eve.dev/docs as a fallback.
Before implementing an integration yourself, use
eve registry search <query> or eve registry list to discover available
integrations. Inspect one with eve registry view <item>, then install it with
eve add <item>.
Motion
Every UI element that animates — components, sections, overlays, state changes —
follows .cursor/rules/motion.mdc, which encodes Emil Kowalski's animation
philosophy. Read it before adding or changing any transition, and consult the
full catalog at .agents/skills/improve-animations/AUDIT.md for exact curve and
duration values. Never invent a cubic-bezier; use the ease-out,
ease-in-out, and ease-drawer tokens in app/globals.css.
Loading
Section and page loads use layout-matching inline skeletons
(.cursor/rules/loading-skeletons.mdc). Never use a lone spinner or “Loading…”
text for a content region — mirror the real layout with Skeleton.
Pages
Every app/**/page.tsx and layout is a Server Component by default
(.cursor/rules/server-pages.mdc). Never add "use client" to pages — extract
interactive UI into components/** and import it.
Buttons
Async action buttons use loading on @/components/ui/button with a progressive
label (Log in → Logging in…). See .cursor/rules/button-loading.mdc.
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices.
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.
- yesterday First seen · 49 lines · 553 tokens per session scan A 49be2a710f77
knowledge-agent-template AGENTS.md is an instructions file published in the GitHub repository azacdev/knowledge-agent-template (2 stars, last pushed 6d ago), licensed MIT. It adds 553 tokens to every session, about $0.0028 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
Paperlab AGENTS.md
Instructions for NourMtir0722/Paperlab, covering paperlab — for coding agents, integrating paperlab into a project, stage mode — paper as architecture, content types and lighting is data, not an enum.
markdy-com copilot-instructions.md
Instructions for HoangYell/markdy-com, a project described as: 🎬 Open-source animated architecture diagrams as code. Diagram-native DSL, 17 layout engines, Web Animations API, and MCP server for AI agents.
diffusers AGENTS.md
Instructions for huggingface/diffusers, a project described as: 🤗 Diffusers: State-of-the-art diffusion models for image, video, and audio generation in PyTorch.
comfy-prompt-studio AGENTS.md
Instructions for yxhpy/comfy-prompt-studio, covering agents.md - ai 代理配置文档, ai 提供商, 1. ollama (默认), 2. gemini and 提示词生成服务.
davinci-resolve-mcp AGENTS.md
Instructions for apvlv/davinci-resolve-mcp, covering project knowledge base, structure, where to look, code map and conventions.
lianhuanhua-skills AGENTS.md
Instructions for littlewindy123/lianhuanhua-skills, covering agents.md, project goal, architecture rules, commands and before committing.