Borrowing it
Nothing to install: this file belongs to TalonT-Org/AutoSkillit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TalonT-Org/AutoSkillit/main/.claude/skills/make-scenarios/SKILL.mdgit clone --depth 1 https://github.com/TalonT-Org/AutoSkillitWrote 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/talont-org/autoskillit/make-scenarios)<a href="https://agentmods.dev/skills/talont-org/autoskillit/make-scenarios"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/make-scenarios.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.1 | $0.00054 | $0.01488 |
| Opus 5 | $0.00027 | $0.00744 |
| Sonnet 5 | $0.00011 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
make-scenarios 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario Generation Skill
Analyze a plan, codebase, or feature description and produce scenarios — statements of what an actor wants to be able to do. Scenarios are perspective-driven: the user provides the lens (developer extensibility, end-user capability, operator workflow, security posture, etc.) and the skill discovers what scenarios matter from that perspective.
Scenarios follow the form: "{Actor} wants to {action} {target}"
These scenarios become input for requirements generation via /make-req in a separate session.
When to Use
- User says "make scenarios", "generate scenarios", "jeopardy requirements"
- User wants to discover extension points, use cases, or capability gaps
- User wants to understand what a system should accommodate from a specific perspective
Core Principles
- Scenarios are perspective-dependent. The same codebase yields different scenarios for a developer vs. an end-user vs. an operator. The user provides the perspective.
- Scenarios state desires, not solutions. Each scenario says what an actor wants to achieve, never how the system should enable it.
- Scenarios are discovered, not invented. They emerge from what the codebase or plan reveals — variation points, hardcoded assumptions, existing abstractions, domain concepts.
Critical Constraints
NEVER:
- Modify any source code files
- Create files outside
temp/make-scenarios/directory - Prescribe solutions or approaches in scenarios
- Invent scenarios that have no basis in the analyzed material
- Mix perspectives in a single scenario (each scenario has one actor type)
ALWAYS:
- Require the user to state the perspective/lens before proceeding
- Use subagents for parallel exploration
- Ground every scenario in evidence from the codebase or plan
- Write output to
temp/make-scenarios/directory
Workflow
Step 0: Establish Perspective
If the user has not stated a perspective, ask. Examples:
- Developer extensibility: "Developer wants to add/swap/extend..."
- End-user capability: "User wants to filter/export/customize..."
- Operator workflow: "Operator wants to monitor/configure/rotate..."
- Security posture: "Attacker wants to escalate/exfiltrate/bypass..."
- Data analyst: "Analyst wants to query/export/visualize..."
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.
- 7d ago First seen · 172 lines · 54 tokens per session scan A 63893c84683c
make-scenarios is a skill published in the GitHub repository TalonT-Org/AutoSkillit (5 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 1,488 once invoked, about $0.0003 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.
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…
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…