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-signoff/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-signoff)<a href="https://agentmods.dev/skills/opendatahub-io/strat-creator/strategy-signoff"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-signoff/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-signoff"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-signoff.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.01109 |
| Opus 5 | $0.00015 | $0.00554 |
| Sonnet 5 | $0.00006 | $0.00222 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
strategy-signoff 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 11d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are signing off on a strategy that has passed CI review, marking it as feature-ready after human confirmation.
Input
$ARGUMENTS must contain a RHAISTRAT key (e.g., RHAISTRAT-1520). If no key is provided, ask the user for one.
Step 1: Validate Pre-Conditions
Read the strategy file from local/strat-tasks/RHAISTRAT-NNNN.md. Verify it exists.
Then fetch the current labels and parent from Jira:
python3 ${CLAUDE_SKILL_DIR}/scripts/fetch_issue.py RHAISTRAT-NNNN --fields labels,parent --markdown
Guard checks:
- If the issue has
strat-creator-needs-attention(notrubric-pass): tell the user this strategy needs CI approval first. Suggest using/strategy-pushto resubmit, then waiting for CI to approve before signing off. Stop here. - If the issue does NOT have
strat-creator-rubric-pass: tell the user this strategy hasn't been CI-approved yet and cannot be signed off. Stop here. - If the local file does not exist: tell the user to run
/strategy-pull RHAISTRAT-NNNNfirst. Stop here.
Parent check (non-blocking):
- If the issue has no
parentfield set: print[WARNING] RHAISTRAT-NNNN has no parent Outcome set. Consider setting one in Jira for proper hierarchy navigation.Continue with sign-off.
Step 2: Confirm with User
Before proceeding, show the user a summary:
- Read the local strategy file and display the title and key sections
- If a local review exists in
local/strat-reviews/, show the score summary
Ask the user to confirm: "Ready to sign off on RHAISTRAT-NNNN? This will push the strategy content to Jira and add the strat-creator-human-sign-off label."
Step 3: Push Strategy Content
Push the updated strategy section to Jira:
python3 ${CLAUDE_SKILL_DIR}/scripts/push_strategy.py RHAISTRAT-NNNN local/strat-tasks/RHAISTRAT-NNNN.md
Step 4: Post Review Summary Comment
If a review summary exists at local/strat-reviews/RHAISTRAT-NNNN-review-summary.md, post it as a comment to the Jira issue:
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.
- 11d ago First seen · 112 lines · 30 tokens per session scan A 0b48cf0fa904
strategy-signoff is a skill published in the GitHub repository opendatahub-io/strat-creator (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,109 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.