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 commands/worc4021/ampl-mcp/ampl-explaingit clone --depth 1 https://github.com/worc4021/ampl-mcpWrote 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/commands/worc4021/ampl-mcp/ampl-explain)<a href="https://agentmods.dev/commands/worc4021/ampl-mcp/ampl-explain"><img src="https://agentmods.dev/badge/commands/worc4021/ampl-mcp/ampl-explain.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.00014 | $0.00167 |
| Opus 5 | $0.00007 | $0.00084 |
| Sonnet 5 | $0.00003 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
ampl-explain 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.
What it actually says
Explain the current solution.
- Call
ampl_solveif no solve has happened yet in this session. - For each constraint, read
ampl_get_data(name, suffix="dual")andampl_get_data(name, suffix="slack")(one suffix per call). - Identify the binding constraints (slack near zero) and report their shadow prices in plain language: what one more unit of that resource would be worth.
- Read
suffix="rc"on the variables and explain any that sit at a bound. - If the model did not solve (
okis not true), callampl_diagnoseand explain instead.
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 · 15 lines · 14 tokens per session scan A 478adcfaffe0
ampl-explain is a command published in the GitHub repository worc4021/ampl-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 167 once invoked, 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-31.
Other commands, from other repositories
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
master_analysis
Run comprehensive 5-phase analysis across labs, genetics, and protocols.
run-panguweather
Guide the user through running PanguWeather end-to-end on an AMD cluster.
render-figures
Compile all .tex and .typ figure files in a directory.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.