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/udecode/plate-playground-template/agents-mdgit clone --depth 1 https://github.com/udecode/plate-playground-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/udecode/plate-playground-template/agents-md)<a href="https://agentmods.dev/instructions/udecode/plate-playground-template/agents-md"><img src="https://agentmods.dev/badge/instructions/udecode/plate-playground-template/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.01389 | $0.01389 |
| Opus 5 | $0.00694 | $0.00694 |
| Sonnet 5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
plate-playground-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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plate-template AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.agents/AGENTS.mdand.agents/rules/*.mdcare source of truth. After editing them, runbun installto sync. Never editSKILL.mddirectly.- In all interactions and commit messages, be extremely concise and sacrifice grammar for the sake of concision.
- ALWAYS read and understand relevant files before proposing edits. Do not speculate about code you have not inspected.
- Never browse GitHub files. For library/API questions or unfamiliar deps, inspect the repo at
..; if missing, clonehttps://github.com/{owner}/{repo}.gitto../{repo-name}. - For repo research, use
spawn_agent(... agent_type=\"explorer\")and return file-backed findings from docs, structure, exports, examples, and tests only. - Dirty workspace: Never pause to ask about unrelated local changes. Continue work and ignore unrelated diffs.
- Proactively use Skill(tdd) when it adds value; skip TDD for high-friction tests like slow React or browser flows.
Skill Overrides
When using the following skills, override the default behavior.
planning-with-files:
- Do not create
task_plan.md,findings.md, orprogress.mdat repo root. Merge that content into one file underdocs/plans/. Example:docs/plans/2026-03-11-task.md
Browser usage:
- Always try
[@browser-use](plugin://browser-use@openai-bundled)first for browser usage. - Do not substitute Puppeteer, standalone Playwright, or raw Chrome DevTools for browser usage.
ce-*:
- Git: Never git add, commit, push, or create PR unless the user explicitly asks.
- PR: Before creating or updating a PR, run the local verification that actually matters here. At minimum:
bun run typecheck,bun run lint:fix, andbun run buildif the task touched app behavior or build config. - plan: Include Browser Use in acceptance criteria for browser features.
- deepen-plan: Context7 only when not covered by skills.
- work: UI tasks require browser verification before marking complete. Never guess.
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.
- 4d ago First seen · 104 lines · 1,389 tokens per session scan A 2752643a788a
plate-playground-template AGENTS.md is an instructions file published in the GitHub repository udecode/plate-playground-template (240 stars, last pushed 14d ago), licensed MIT. It adds 1,389 tokens to every session, about $0.0069 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-30.
Other instructions, from other repositories
plate-template AGENTS.md
Instructions for udecode/plate-template, covering skill overrides, commands, development, prompt hook and mandatory first response.
plate-template CLAUDE.md
Instructions for udecode/plate-template, a project described as: Minimal Plate template with React 19, Next 16, Tailwind 4, MCP.
coss AGENTS.md
AGENTS.md instructions for cosscom/coss, covering agents.md and main documentation.
next-shadcn-dashboard-starter AGENTS.md
Instructions for Kiranism/next-shadcn-dashboard-starter, covering agents.md - ai coding agent reference, project overview, technology stack details, core framework & runtime and styling & ui.
next-shadcn-dashboard-starter CLAUDE.md
Instructions for Kiranism/next-shadcn-dashboard-starter, covering claude.md, key references and critical conventions.
fulling AGENTS.md
Instructions for FullAgent/fulling, covering agents.md, project overview, tech stack, code conventions and current implementation context.