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/pycaret/pycaret/agents-mdgit clone --depth 1 https://github.com/pycaret/pycaretWrote 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/pycaret/pycaret/agents-md)<a href="https://agentmods.dev/instructions/pycaret/pycaret/agents-md"><img src="https://agentmods.dev/badge/instructions/pycaret/pycaret/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.03455 | $0.03455 |
| Opus 5 | $0.01728 | $0.01728 |
| Sonnet 5 | $0.00691 | $0.00691 |
| Haiku 4.5 | $0.00346 | $0.00346 |
Grade A, and why
pycaret 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 3d 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.
- 3d ago First seen · 187 lines · 3,455 tokens per session scan A 6835fd31085f
pycaret AGENTS.md is an instructions file published in the GitHub repository pycaret/pycaret (9,833 stars, last pushed 1mo ago), with no licence file. It adds 3,455 tokens to every session, about $0.0173 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
mlflow CLAUDE.md
Claude Code instructions for mlflow/mlflow, covering claude.md, knowledge cutoff note, code style principles, repository overview and quick start: development server.
marimo AGENTS.md
Instructions for marimo-team/marimo, covering marimo development guidelines, your primary responsibility is to the project and its users, quick setup, development commands and python.
streamlit copilot-instructions.md
Copilot instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.
mlflow code-review.instructions.md
Instructions for mlflow/mlflow, covering code review instructions, knowledge cutoff and do not comment on.
zenml CLAUDE.md
Claude Code instructions for zenml-io/zenml, covering zenml claude code guidelines, project structure, use zenml docs via mcp, code style & quality standards and commenting policy — explain why, not what.
marimo copilot-instructions.md
Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?