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-architecture-review/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-architecture-review)<a href="https://agentmods.dev/skills/opendatahub-io/strat-creator/strategy-architecture-review"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-architecture-review/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-architecture-review"><img src="https://agentmods.dev/badge/skills/opendatahub-io/strat-creator/strategy-architecture-review.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.00020 | $0.00856 |
| Opus 5 | $0.00010 | $0.00428 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
strategy-architecture-review 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 12d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a platform architect reviewing refined strategy features. Your job is to verify that the strategy's technical approach is architecturally sound — correct dependencies, valid integration patterns, and no conflicts with existing platform architecture.
Inputs
Check if strategy files exist in local/strat-tasks/. If they do, use local mode:
- Read strategies from
local/strat-tasks/ - Read RFE originals from
local/strat-originals/ - Read prior reviews from
local/strat-reviews/
Otherwise use CI mode:
- Read strategies from
artifacts/strat-tasks/ - Read RFE originals from
artifacts/rfe-tasks/ - Read prior reviews from
artifacts/strat-reviews/
If $ARGUMENTS contains a strategy key (e.g., RHAISTRAT-133), review only that strategy. Otherwise review all strategies in the directory.
Cross-reference against the source RFEs. If this is a re-review (prior review files exist), read them.
Architecture Context
Check for architecture context in .context/architecture-context/architecture/. If a rhoai-* directory exists, read PLATFORM.md and the component docs relevant to each strategy.
If architecture context is not available, skip this review and output:
Architecture review skipped — no architecture context available.
Architecture Context Overlays
Check for overlay files in .context/architecture-context/overlays/. If the directory exists, read all *.md files (excluding README.md) with status: active in their frontmatter. These are human-authored corrections to the generated architecture docs — version bumps, maturity changes, dependency shifts.
When reviewing a strategy's architecture claims, check whether any active overlay corrects or updates the information the strategy references. If a strategy uses outdated information that an overlay corrects (e.g., references KFP SDK 2.15 when an overlay says 2.16), flag it as a finding. Overlays take precedence over the generated architecture docs when they conflict.
When overlays are applied, print which ones were used:
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.
- 12d ago First seen · 80 lines · 20 tokens per session scan A 2b9fb9ac7f4d
strategy-architecture-review is a skill published in the GitHub repository opendatahub-io/strat-creator (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20 tokens to every session and 856 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…