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/ansys/pymapdl/reviewergit clone --depth 1 https://github.com/ansys/pymapdlWrote 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/ansys/pymapdl/reviewer)<a href="https://agentmods.dev/instructions/ansys/pymapdl/reviewer"><img src="https://agentmods.dev/badge/instructions/ansys/pymapdl/reviewer.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.00017 | $0.00017 |
| Opus 5 | $0.00009 | $0.00009 |
| Sonnet 5 | $0.00003 | $0.00003 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
pymapdl reviewer.instructions.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 5d 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
The reviewer follows the guidelines given in .github/agents/reviewer.agent.md.
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.
- 5d ago First seen · 3 lines · 17 tokens per session scan A 5fed73a30c31
pymapdl reviewer.instructions.md is an instructions file published in the GitHub repository ansys/pymapdl (514 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session, about $0.0001 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
rune CLAUDE.md
Instructions for Rune-kit/rune, covering rune — project configuration, tech stack, directory structure, mandatory skill routing and conventions.
mesh-api AGENTS.md
AGENTS.md instructions for mr-tbot/mesh-api, covering mesh-api — agent guide, build / run, architecture, adding an extension and conventions & pitfalls.
bproc-pubvis AGENTS.md
AGENTS.md instructions for hummat/bproc-pubvis, covering agents.md, conventions, project overview, development commands and setup.
agent-comms AGENTS.md
AGENTS.md instructions for ExaDev/agent-comms, a project described as: Cross-harness communication mesh for LLM agents. Rooms, DMs, presence, and visibility.
agent-comms CLAUDE.md
Claude Code instructions for ExaDev/agent-comms, a project described as: Cross-harness communication mesh for LLM agents. Rooms, DMs, presence, and visibility.
ansys-aedt-mcp AGENTS.md
AGENTS.md instructions for LaplaceYoung/ansys-aedt-mcp, a project described as: MCP server for Ansys Electronics Desktop automation with PyAEDT, HFSS, Maxwell, Q3D, Icepak, native AEDT APIs, reports, sweeps, and simulation workflows.