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.
git clone --depth 1 https://github.com/llama-farm/llamafarmWrote 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/llama-farm/llamafarm/formatting)<a href="https://agentmods.dev/rules/llama-farm/llamafarm/formatting"><img src="https://agentmods.dev/badge/rules/llama-farm/llamafarm/formatting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/llama-farm/llamafarm/formatting"><img src="https://agentmods.dev/badge/rules/llama-farm/llamafarm/formatting.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00074 | $0.00074 |
| Opus 5.5 | $0.00030 | $0.00030 |
| Sonnet 5.5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
formatting 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 1mo 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
Formatting rules to follow
Always adhere to these formatting rules when modifying files with the specified content type
YAML
- Prefer no quotes for strings
- Use double quotes for strings if necessary
Javascript
- Use single quotes for strings unless otherwise required
TypeScript
- Use single quotes for strings unless otherwise required
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.
- 1mo ago First seen · 17 lines · 74 tokens per session scan A 81d3a64e57db
formatting is a cursor rule published in the GitHub repository llama-farm/llamafarm (835 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 74 tokens to every session, about $0.0003 per session on Opus 5.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 cursor rules, from other repositories
cache-optimization
Fantasy402 cache optimization patterns and performance guidelines.
cloudflare-infrastructure
Cloudflare infrastructure patterns and best practices.
endpoint-routing
Endpoint routing patterns and request handling conventions.
99-floor
AI Floor - Single source of truth for autonomous operations.
api-patterns
API endpoint patterns and request handling conventions.
code-searchability
Code searchability patterns and ast-grep integration.