DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check prices before running a generation batch with Skills

Have an agent price a planned batch in Scenario before spending credits on it.

  • Content
  • Intermediate
  • 15 minutes
  • From the README
  • Claude Code
  • Cursor
  • Codex

Who it is forA content producer who must stay within a fixed budget when generating many images or videos.

The problemRunning a large batch without checking cost first can use up the budget on the wrong settings.

The outcomeA priced plan for the batch, approved or changed before any generation runs.

What you need first

  • A Scenario account, signed in through OAuth or an API key
  • An AI coding agent that supports Agent Skills, such as Claude Code, Cursor, or Codex
  • npx, to run the skills installer
  • The Scenario MCP server connected to the agent at https://mcp.scenario.com/mcp

Steps

  1. npx skills add scenario-labs/skills --skill scenario
  2. Connect the Scenario MCP server to your agent, using claude mcp add --transport http scenario https://mcp.scenario.com/mcp for Claude Code.
  3. List the planned generations with model and size for each one.
  4. Ask the agent to price the whole batch and show the total before it runs anything.
  5. Approve, trim, or change the settings, then start the run.

Prompt for your agent

Using the scenario-labs/skills repo, price a batch of <count> generations described in <batch-file> before running any of them. Report the total cost and the cost per item. Verify that no generation starts until I approve the total.

Caveat. The Skills say they price before spending, but the price check only covers the generations you list, so add any new items to the plan before approving.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page