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-pull/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-pull)<a href="https://agentmods.dev/skills/opendatahub-io/strat-creator/strategy-pull"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-pull/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-pull"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-pull.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.00030 | $0.00731 |
| Opus 5 | $0.00015 | $0.00365 |
| Sonnet 5 | $0.00006 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
strategy-pull 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pulling a strategy from Jira into the local workspace so a human can review and iterate on it.
Input
$ARGUMENTS must contain a RHAISTRAT key (e.g., RHAISTRAT-1520). If no key is provided, ask the user for one.
Pull the Strategy
Run the pull script:
python3 ${CLAUDE_SKILL_DIR}/scripts/pull_strategy.py $ARGUMENTS
This will:
- Validate the strategy has a post-CI label (
strat-creator-rubric-passorstrat-creator-needs-attention) - Fetch the strategy description from Jira
- Write
local/strat-tasks/RHAISTRAT-NNNN.mdwithworkflow: localfrontmatter - Fetch the linked RFE original and comments into
local/strat-originals/ - Fetch the review summary comment and full review attachment into
local/strat-reviews/ - Archive any existing version history and save the pulled strategy as the v0 baseline:
python3 scripts/strategy_history.py reset local/strat-tasks/RHAISTRAT-NNNN.md
python3 scripts/strategy_history.py save local/strat-tasks/RHAISTRAT-NNNN.md
The pull creates three folders under local/:
strat-tasks/— The strategy document itself (e.g.,RHAISTRAT-133.md). This is what you review and edit.strat-originals/— The source RFE snapshot and its comments at pull time. Read-only context for understanding the business need.strat-reviews/— CI review output. Contains two files per strategy:RHAISTRAT-NNNN-review-summary.md— The scoring table and verdict (pass/fail, scores per criterion).RHAISTRAT-NNNN-review.md— The full prose review from independent reviewers (detailed analysis per dimension).
If the script exits with code 1 (missing labels or not found), explain that only post-CI strategies can be pulled. If code 2 (missing credentials), tell the user to set JIRA_SERVER, JIRA_USER, and JIRA_TOKEN.
After Pulling
Read the pulled strategy file and the review file (if present). Summarize for the user:
- Strategy title and priority
- CI verdict: approved (rubric-pass) or needs attention
- Review highlights: if a review file was pulled, summarize the key findings
- Source RFE: which RFE this strategy is derived from
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 · 60 lines · 30 tokens per session scan A 80fbda7b5bb3
strategy-pull is a skill published in the GitHub repository opendatahub-io/strat-creator (2 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 731 once invoked, about $0.0002 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.