ampl-scenario

ampl-scenario is a command for Claude Code from worc4021/ampl-mcp. It costs 11 tokens per session (199 once invoked), scanned A, original, MIT.

A command for AMPL, a modeling language used for optimization, that tests one model parameter across several values and records the resulting objective.

In plain words
What is it for?
Use it for what-if analysis, such as checking how different costs, capacities, or demand values affect an optimization model.
Why use it?
It avoids repeating manual solves when comparing alternatives. It also shows when results change, stay flat, or fail to solve.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the ampl plugin — 1 skill, 3 commands, 1 MCP server shipped together

Good fit Use it for what-if analysis, such as checking how different costs, capacities, or demand values affect an optimization model.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/worc4021/ampl-mcp/ampl-scenario
Install

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.

Clone the repo
git clone --depth 1 https://github.com/worc4021/ampl-mcp

Made for: Claude Code.

Or install ampl, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 MCP server.

Wrote 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.

agentmods badge for ampl-scenario

README.md
[![agentmods](https://agentmods.dev/badge/commands/worc4021/ampl-mcp/ampl-scenario.svg)](https://agentmods.dev/commands/worc4021/ampl-mcp/ampl-scenario)
Your own site
<a href="https://agentmods.dev/commands/worc4021/ampl-mcp/ampl-scenario"><img src="https://agentmods.dev/badge/commands/worc4021/ampl-mcp/ampl-scenario.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 199 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00199
Opus 5 $0.00005 $0.00100
Sonnet 5 $0.00002 $0.00040
Haiku 4.5 $0.00001 $0.00020

Measured 6d ago against content hash da026ecf47c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

ampl-scenario 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 6d 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.

commands/ampl-scenario.md · 18 lines

What it actually says

Run a what-if study over $ARGUMENTS (expected: a parameter name and a list of values).

  1. Confirm a session exists with ampl_list_sessions; if not, say so and stop.
  2. Confirm the parameter exists with ampl_list_entities.
  3. Call ampl_sweep with the parameter and values, collecting the objective.
  4. Present the results as a table: value, objective, solve status, time.
  5. Comment on the shape of the response - where it is flat, where it turns, and any value that failed to solve.
  6. Remember that ampl_sweep leaves the parameter set to the last value it swept to. If further work in this session depends on the parameter's original value, re-set it explicitly (e.g. via ampl_set_data) before continuing.
Changes

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.

  1. 6d ago First seen · 18 lines · 11 tokens per session scan A da026ecf47c7

Subscribe to this mod's changes

ampl-scenario is a command published in the GitHub repository worc4021/ampl-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 199 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.