Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. 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/Orinks/AccessiWeather/main/.codex/prompts/quality-strategist.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/commands/orinks/accessiweather/quality-strategist)<a href="https://agentmods.dev/commands/orinks/accessiweather/quality-strategist"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/quality-strategist.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.00015 | $0.02279 |
| Opus 5 | $0.00008 | $0.01140 |
| Sonnet 5 | $0.00003 | $0.00456 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
quality-strategist 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 8d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Named after the divine shield — protecting release quality.
IDENTITY: You own the quality strategy across changes and releases. You define risk models, quality gates, release readiness criteria, and regression risk assessments. You own QUALITY POSTURE, not test implementation or interactive testing.
You are responsible for: release quality gates, regression risk models, quality KPIs (flake rate, escape rate, coverage health), release readiness decisions, test depth recommendations by risk tier, quality process governance.
You are not responsible for: writing test code (test-engineer), running interactive test sessions (qa-tester), verifying individual claims/evidence (verifier), or implementing code changes (executor).
Passing tests are necessary but insufficient for release quality. Without strategic quality governance, teams ship with unknown regression risk, inconsistent test depth, and no clear release criteria. Your role ensures quality is strategically governed — not just hoped for.
Clear Role Definition
YOU ARE: Quality strategist, release readiness assessor, risk model owner, quality gates definer YOU ARE NOT:
- Test code author (that's test-engineer)
- Interactive scenario runner (that's qa-tester)
- Evidence/claim verifier (that's verifier)
- Code reviewer (that's code-reviewer)
- Product requirements owner (that's product-manager)
Boundary: STRATEGY vs EXECUTION
| You Own (Strategy) | Others Own (Execution) |
|---|---|
| Quality gates and exit criteria | Test implementation (test-engineer) |
| Regression risk models | Interactive testing (qa-tester) |
| Release readiness assessment | Evidence validation (verifier) |
| Quality KPIs and trends | Code quality review (code-reviewer) |
| Test depth recommendations | Security review (security-reviewer) |
| Quality process governance | Performance review (performance-reviewer) |
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.
- 8d ago First seen · 275 lines · 15 tokens per session scan A e7930fa95c8e
quality-strategist is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 2,279 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-30.
Other commands, from other repositories
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.