Borrowing it
Nothing to install: this file belongs to opendatahub-io/strat-creator. 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/opendatahub-io/strat-creator/main/.claude/skills/strategy-create/SKILL.mdgit clone --depth 1 https://github.com/opendatahub-io/strat-creatorWrote 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/opendatahub-io/strat-creator/strategy-create)<a href="https://agentmods.dev/skills/opendatahub-io/strat-creator/strategy-create"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-create/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.
<a href="https://agentmods.dev/skills/opendatahub-io/strat-creator/strategy-create"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-create.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.04520 |
| Opus 5 | $0.00014 | $0.02260 |
| Sonnet 5 | $0.00006 | $0.00904 |
| Haiku 4.5 | $0.00003 | $0.00452 |
Grade A, and why
strategy-create 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 9d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a strategy creation assistant. Your job is to create strategies from approved RFEs by cloning them into the RHAISTRAT project, then setting up local artifacts for refinement.
Dry Run Mode
If --dry-run is in $ARGUMENTS, skip ALL external writes:
- Do NOT clone issues in Jira (skip Step 3 entirely)
- Do NOT create or edit any Jira issues
- DO still fetch RFE data from Jira (reads are safe)
- DO still create local artifacts in
artifacts/strat-tasks/ - For Path B (no existing STRAT): Set
jira_key=nullon stubs since no Jira issues were created. Use the RFE number as the strat ID (e.g., RHAIRFE-1146 →STRAT-1146, filenameSTRAT-1146.md) - For Path A (existing STRAT found via Cloners link): Use the real
RHAISTRAT-NNNNkey as filename andjira_key— the ticket already exists, we're importing it - Print
[DRY RUN] Skipping Jira clone for <RFE key>for each Path B RFE
Step 1: Find RFE Source Data
Check for available RFE sources:
- Local artifacts — check for
artifacts/rfe-tasks/files with valid frontmatter. Read Jira keys from task file frontmatter:
python3 ${CLAUDE_SKILL_DIR}/scripts/frontmatter.py read artifacts/rfe-tasks/<file>.md
- Jira — check if Jira MCP is available or if
JIRA_SERVER/JIRA_USER/JIRA_TOKENenv vars are set, and if the user has provided RHAIRFE keys
If both local artifacts and Jira are available: Ask the user which source to use. Local artifacts may have been edited after submission; Jira has the canonical version. Let the user decide.
If only local artifacts exist: Use them.
If only Jira keys are available: Fetch from Jira. Try mcp__atlassian__getJiraIssue first. If the MCP tool is unavailable, fall back to the REST API script:
python3 ${CLAUDE_SKILL_DIR}/scripts/fetch_issue.py RHAIRFE-1234 --fields summary,description,priority,labels,status --markdown
The script outputs JSON to stdout with the description already converted to markdown. Parse the fields to build local artifacts.
What ships with it
1 file 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.
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.
- 9d ago First seen · 320 lines · 28 tokens per session scan A 4a50491c5a2d
strategy-create is a skill published in the GitHub repository opendatahub-io/strat-creator (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 4,520 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.