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 rules/asap-protocol/agentic-orchestration/frontend-best-practicesgit clone --depth 1 https://github.com/asap-protocol/agentic-orchestrationWrote 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/rules/asap-protocol/agentic-orchestration/frontend-best-practices)<a href="https://agentmods.dev/rules/asap-protocol/agentic-orchestration/frontend-best-practices"><img src="https://agentmods.dev/badge/rules/asap-protocol/agentic-orchestration/frontend-best-practices.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.00779 | $0.00779 |
| Opus 5 | $0.00390 | $0.00390 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
frontend-best-practices 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 62 lines · 779 tokens per session scan A 9ed6710849a2
frontend-best-practices is a cursor rule published in the GitHub repository asap-protocol/agentic-orchestration (10 stars, last pushed 11d ago), with no licence file. It adds 779 tokens to every session, about $0.0039 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 cursor rules, from other repositories
frontend-best-practices
Standards for modern Frontend development using Next.js 16 (App Router), React 19, Tailwind CSS v4, and Shadcn/UI. Apply when working on apps/web or packages/ui.
react
Cursor rule "react" from iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
01-code-style
Cursor rule "01-code-style" from refly-ai/refly, covering code style guidelines, typescript/javascript style, react performance optimization, error handling and css guidelines.
components
React components — shadcn/ui, RTL, theme, and client/server boundaries.
react-meta-patterns
React Meta framework defaults for Platform 3.0 UI apps — metaConfig, DEW components, React Router, optional Tailwind/vite, custom HTML placement. Use when creating or migrating Meta apps.
ui
UI/dashboard rules — vanilla JS, no frameworks.