ambitious-model-use

ambitious-model-use is a skill for Claude Code from sammcj/agentic-coding. It costs 58 tokens per session (834 once invoked), scanned A, original, Apache-2.0.

A guide for making an AI task more ambitious by clarifying the desired outcome, using raw data, and drawing on relevant fields. It also identifies what access and outside checks the task needs.

In plain words
What is it for?
Use it when you want an AI task rewritten around a decision, meeting, metric, dataset, or deeper expert workflow.
Why use it?
It helps avoid shallow prompt rewrites that miss the real goal or lack the data and tools needed to judge the result. It asks for confirmation before carrying out the expanded task.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents.

Good fit Use it when you want an AI task rewritten around a decision, meeting, metric, dataset, or deeper expert workflow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sammcj/agentic-coding/ambitious-model-use
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.

Any agent
npx skills add sammcj/agentic-coding --skill ambitious-model-use
Clone the repo
git clone --depth 1 https://github.com/sammcj/agentic-coding

Made for: Claude Code.

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 ambitious-model-use

README.md
[![agentmods](https://agentmods.dev/badge/skills/sammcj/agentic-coding/ambitious-model-use/github.svg)](https://agentmods.dev/skills/sammcj/agentic-coding/ambitious-model-use)
Your own site
<a href="https://agentmods.dev/skills/sammcj/agentic-coding/ambitious-model-use"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/ambitious-model-use/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ambitious-model-use

Your own site · 80×15
<a href="https://agentmods.dev/skills/sammcj/agentic-coding/ambitious-model-use"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/ambitious-model-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 834 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.00058 $0.00834
Opus 5.5 $0.00023 $0.00334
Sonnet 5.5 $0.00012 $0.00167
Haiku 4.5 $0.00006 $0.00083

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

Security

Grade A, and why

ambitious-model-use 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 2d 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.

Skills/ambitious-model-use/SKILL.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ambitious Model Use - Altitude, Depth and Range

Workflow

  1. Create a task per step below, each with its completion criterion.
  2. Diagnose the request on each dimension:
    • Altitude: deliverable, or the outcome behind it? Strongest when the work ends in a meeting or decision; weak for open creative work.
    • Depth: raw data and the instruments a field-leading expert uses, or digested summaries? Fits any task the user wants done really well.
    • Range: only the field the task names on its surface? Strongest for creative work.
  3. Pick the dimensions with the largest gap and write the rewritten brief using the techniques below. Read references/examples.md first for worked QBR, churn and homepage rewrites.
  4. List the access the brief needs (a computer, installable tools, raw data via files or MCP connectors) and flag what is missing.
  5. Name the outside judge: a tool, metric or held-out dataset the model runs. The model's own judgement does not count.
  6. Present steps 2-5 to the user. Execute the brief only after the user confirms it, applying the Depth and Range techniques yourself.

Altitude Techniques

  • Ask the user "what do you want to happen next?" instead of assuming the goal. Only the user can answer it.
  • Move from "fix crashes" to "keep the app crash-free". Durable outcomes need workflow changes first: crash-report access, a version-to-commit map, and machines to reproduce and verify fixes.
  • Decompose open-ended goals ("go make money") into outcomes the model can verify.

Depth Techniques

Models often change vocabulary without changing methods. Insist on the instruments the best practitioners use.

  • Demand databases, statistical models, simulations or domain tools instead of markdown tables.
  • Set unreasonable targets and call them reasonable (5 s load time needed -> ask for 200 ms). When the model calls something impossible, restate that it is solvable and have it keep going.
  • Adversarially check assumptions against raw data: "We believe X. Try to reproduce that from the raw data."
  • Produce new knowledge: build a simulation that reproduces historical data, then find the earliest unknown predictive signal and test it on held-out data.

Read the full file on GitHub · 49 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 49 lines · 58 tokens per session scan A f2e4e6df65df

Subscribe to this mod's changes

ambitious-model-use is a skill published in the GitHub repository sammcj/agentic-coding (165 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 834 once invoked, about $0.0002 per session on Opus 5.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-10-19.