Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Day1Labs/OpenAva --skill strategy-reviewgit clone --depth 1 https://github.com/Day1Labs/OpenAvaWrote 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/day1labs/openava/strategy-review)<a href="https://agentmods.dev/skills/day1labs/openava/strategy-review"><img src="https://agentmods.dev/badge/skills/day1labs/openava/strategy-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/day1labs/openava/strategy-review"><img src="https://agentmods.dev/badge/skills/day1labs/openava/strategy-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.00023 | $0.01462 |
| Opus 5 | $0.00012 | $0.00731 |
| Sonnet 5 | $0.00005 | $0.00292 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
strategy-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 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Review
Use this skill when the user asks things like:
- Think bigger.
- Rethink this plan.
- Is this ambitious enough?
- Hold scope but review it hard.
- Cut this down to the minimum viable version.
This is a strategic review skill for plans, proposals, and feature direction. It is not an implementation skill.
How To Use This Skill
- Treat this skill as a review framework, not a fixed script.
- Ground recommendations in the current product, codebase, and constraints when that context is available.
- If only a written plan exists, keep the review useful by focusing on scope, tradeoffs, risks, and decision quality.
- Make scope changes explicit: separate baseline scope, optional expansion, and out-of-scope work.
Core Mindset
- Challenge the premise, not just the details.
- Optimize for real user and business outcomes, not proxy work.
- Prefer complete thinking over shallow shortcuts.
- Keep scope changes explicit; never silently expand or shrink the plan.
- Bias toward simple systems with strong tests, clear ownership, and visible failure modes.
Review Modes
Pick one mode before deep review. If the user already implied a mode, follow it.
1. Scope Expansion
Use when the user wants the boldest version.
- Describe the 10x version.
- Surface adjacent improvements that would make the feature noticeably better.
- Recommend expansions when they materially improve product quality or leverage.
- Keep each expansion explicit so the user can opt in.
2. Selective Expansion
Use when the current scope is the baseline but the user wants optional upgrades.
- Review the current plan rigorously.
- Surface a small set of high-value expansion opportunities.
- Present them as optional additions, not assumptions.
3. Hold Scope
Use when the user wants maximum rigor without changing scope.
- Do not add new product surface area.
- Focus on architecture, edge cases, errors, tests, observability, and rollout risk.
4. Scope Reduction
Use when the current plan is overbuilt or unclear.
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 · 247 lines · 0 tokens per session scan A 33e9329f3f4a
strategy-review is a skill published in the GitHub repository Day1Labs/OpenAva (10 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,462 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
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
oma-scholar
Scholarly research companion using Knows sidecar spec (.knows.yaml). Generates, validates, reviews, queries, and compares structured research-paper sidecars, and fetches them from knows.academy. Use for academic literature search, survey synthesis, paper authoring assistance, and peer review with token-efficient…
browser_cdp
A health check for Python code that produces a score, letter grade, and measures of issues such as complexity, duplication, dead code, dependencies, and architecture.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.