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/amdresearch/ai4science-studio/recipe-readmegit clone --depth 1 https://github.com/AMDResearch/ai4science-studioWrote 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/amdresearch/ai4science-studio/recipe-readme)<a href="https://agentmods.dev/rules/amdresearch/ai4science-studio/recipe-readme"><img src="https://agentmods.dev/badge/rules/amdresearch/ai4science-studio/recipe-readme.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.00000 | $0.00337 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
recipe-readme 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.
What it actually says
Recipe README conventions
When creating or editing a README.md under any model's recipes/<task>/ directory:
Required sections (in order)
-
Title —
# <Model> — <Task> Recipe -
Callout box — Link to ready-to-run scripts:
> **Ready-to-run scripts:** see [`../../examples/`](../../examples/) for `docker_run.sh` and `run_<task>.sh`. -
Prerequisites — Structured list (not prose paragraph):
## Prerequisites - Container: `<image tag>` - GPU: <hardware requirement> - Runtime: <Docker/Apptainer> - Weights: <how to get them> - Data: <how to get it> -
Environment Variables table:
## Environment Variables | Variable | Required | Default | Description | |----------|----------|---------|-------------| | `VAR` | Yes/No | `default` or -- | What it does | -
Quick Start — One-liner to run the task.
-
Details — Prose explanation, code samples, etc.
Healthcare disclaimer
All healthcare/ recipe READMEs must include at the top:
> **Research / engineering use only.** Not for clinical or diagnostic use.
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 · 48 lines · 0 tokens per session scan A fcf8b2ad8af3
recipe-readme is a cursor rule published in the GitHub repository AMDResearch/ai4science-studio (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 337 tokens. 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
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, invoices, statements, regulatory documents, and PDF delivery. Covers report pages, absolute pixel layout, header/footer panels, common elements, verification…
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.