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 skills/echoo19/decision-simulator/evaluate-tradeoffsnpx skills add echoo19/decision-simulator --skill evaluate-tradeoffsgit clone --depth 1 https://github.com/echoo19/decision-simulatorWrote 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/skills/echoo19/decision-simulator/evaluate-tradeoffs)<a href="https://agentmods.dev/skills/echoo19/decision-simulator/evaluate-tradeoffs"><img src="https://agentmods.dev/badge/skills/echoo19/decision-simulator/evaluate-tradeoffs.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.00097 | $0.00489 |
| Opus 5 | $0.00048 | $0.00244 |
| Sonnet 5 | $0.00019 | $0.00098 |
| Haiku 4.5 | $0.00010 | $0.00049 |
Grade A, and why
evaluate-tradeoffs 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 4d 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
Evaluate Tradeoffs
Compare options across the dimensions that are actually decision-driving in this case. Do not blindly enumerate every possible factor.
Method
- Name the options clearly.
- Choose the smallest set of relevant dimensions.
- For each dimension, explain the mechanism behind the difference.
- Identify which dimensions are decisive versus merely nice-to-have.
- Say when one option dominates and why.
- State the conditions that would flip the recommendation.
Common Dimensions
Use only the dimensions that matter here:
- UX
- DX
- system boundaries
- maintainability
- delivery speed
- scalability
- performance
- reliability
- security and privacy
- infra cost
- engineering time
- team coordination overhead
- debugging difficulty
- flexibility
- reversibility
- operational burden
Quality Bar
- Avoid empty labels like "faster" or "cleaner" without explaining what becomes faster or cleaner.
- Make asymmetry visible. Some options will have one major win and three serious liabilities.
- Highlight non-obvious tradeoffs first.
- Prefer saying "Option A dominates because..." over pretending the choice is balanced.
Suggested Output
Options
List the options.
Relevant dimensions
Name the dimensions that matter and why they matter here.
Tradeoff analysis
For each decisive dimension, compare the options with concrete implications.
Dominant option
Name the option that wins on the dimensions that matter most.
If no option clearly dominates, do not hedge — name the deciding unknown: the single missing input that, once resolved, would break the tie. Do not leave this section as "it depends."
Second-order effects
What does this choice change three weeks or three months later? Consider: team behavior, debugging surface, architecture shape, ownership burden, or rule drift.
Recommendation
Make a call and explain what would change the answer.
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.
- 4d ago First seen · 74 lines · 97 tokens per session scan A d1aeb711829f
evaluate-tradeoffs is a skill published in the GitHub repository echoo19/decision-simulator (4 stars, last pushed 3mo ago), licensed MIT. It adds 97 tokens to every session and 489 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…