tradeoff-analysis

tradeoff-analysis is a skill for Claude Code, Codex from Oriolshhh/runware-image-mcp. It costs 13 tokens per session (419 once invoked), scanned A, original, MIT.

A method for comparing multiple approaches against clearly stated criteria, such as risk, effort, complexity, and performance. It uses evidence to support the recommendation.

In plain words
What is it for?
Use it when choosing between technical designs, product directions, or implementation approaches.
Why use it?
It prevents teams from choosing an option by intuition alone or overlooking simpler, safer alternatives.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it when choosing between technical designs, product directions, or implementation approaches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oriolshhh/runware-image-mcp/tradeoff-analysis
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 Oriolshhh/runware-image-mcp --skill tradeoff-analysis
Clone the repo
git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Claude Code, Codex.

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 tradeoff-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/tradeoff-analysis/github.svg)](https://agentmods.dev/skills/oriolshhh/runware-image-mcp/tradeoff-analysis)
Your own site
<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/tradeoff-analysis"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/tradeoff-analysis/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 tradeoff-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/tradeoff-analysis"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/tradeoff-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 419 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.00013 $0.00419
Opus 5 $0.00006 $0.00210
Sonnet 5 $0.00003 $0.00084
Haiku 4.5 $0.00001 $0.00042

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

Security

Grade A, and why

tradeoff-analysis 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 8d 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.

.agents/skills/tradeoff-analysis/SKILL.md · 47 lines

What it actually says

Tradeoff Analysis

Purpose

Make a recommendation defensible by comparing real alternatives against stated criteria instead of asserting a single option.

When to use it

  • Whenever a specialist or the chair must choose between approaches.
  • Before recommending any non-trivial design or product direction.

Instructions

  1. State the decision and the criteria up front (e.g., correctness, user value, complexity, risk, reversibility, effort, performance). Note relative weight.
  2. Identify at least two viable options, including a "do less / reuse / defer" option. Avoid strawmen.
  3. Score each option against each criterion, citing evidence for the score.
  4. Make the reversibility of each option explicit; prefer reversible options under uncertainty.
  5. State the recommendation, the margin by which it wins, and what evidence would change it.

Output format

A comparison: criteria (with weights), options, a per-criterion assessment with citations, the recommendation with its winning margin, and the conditions that would flip the decision.

Anti-patterns

  • Presenting one option as if no alternative exists.
  • Strawman alternatives that exist only to be rejected.
  • Hiding the criteria, or changing them to fit a preferred answer.
  • Ignoring reversibility and effort.

Verification checklist

  • Criteria are stated before options are scored.
  • At least two genuine options are compared with evidence.
  • Reversibility and effort are considered.
  • The conditions that would change the conclusion are stated.

Apply context-discovery before broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read .agent/context/routing.md, load only relevant summaries, and verify critical claims against source.

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. 8d ago First seen · 47 lines · 13 tokens per session scan A 6c322f75016f

Subscribe to this mod's changes

tradeoff-analysis is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 419 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-09-03.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens