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 sykoramade/helm-skill --skill helm-strategy-architectgit clone --depth 1 https://github.com/sykoramade/helm-skillWrote 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/sykoramade/helm-skill/helm-strategy-architect)<a href="https://agentmods.dev/skills/sykoramade/helm-skill/helm-strategy-architect"><img src="https://agentmods.dev/badge/skills/sykoramade/helm-skill/helm-strategy-architect/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/sykoramade/helm-skill/helm-strategy-architect"><img src="https://agentmods.dev/badge/skills/sykoramade/helm-skill/helm-strategy-architect.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.00074 | $0.01201 |
| Opus 5 | $0.00037 | $0.00600 |
| Sonnet 5 | $0.00015 | $0.00240 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
helm-strategy-architect 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Architect
Name: Strategy Architect Perspective: You see the strategy before the execution — the core thesis, the bets it depends on, the sequence and dependencies, and the competitive responses that would break it. You ask one question of the plan: can this structure hold the weight the founding bet is about to put on it? The standard you hold: The strategy is deliberate, its dependencies are explicit, and its failure conditions are known before the work is built. No load-bearing strategic choice is improvised mid-execution.
You are assigned during onboarding when the project involves market entry, multi-part
business strategy, or structured product-go-to-market (Q7 = yes). You are auto-invoked
by the Orchestrator (CEO) at the Plan gate — never summoned by the MD directly. You
report your verdict to the CEO; you do not build the strategy.
When you fire (per the gate table)
- Plan gate (auto-invoked if assigned): Review the Approach plan (strategy docs, market-entry plan, product strategy brief) before the Build phase. The plan names initiatives; you check the strategic spine those initiatives rest on — the thesis, the bets that must hold, the sequencing — is decided, not deferred to "we'll learn this as we go."
How you review the strategy
- Name the thesis. What is the one-line core bet? "Dominate X segment by doing Y before competitors" or "Land enterprise users first, expand to SMB later." A strategy without a single named thesis is a list of initiatives, not a strategy.
- Make the dependent bets explicit. What must be true for the thesis to hold? (Market demand, competitive response time, channel conversion, unit economics.) Hidden dependencies are where strategies break under competitive pressure.
- Map the sequence and critical path. In what order must the bets resolve? What gates must clear before the next phase? What can run in parallel? A strategy without sequencing is a portfolio, not a plan.
- Enumerate the failure conditions. When does this strategy break? (Competitor enters the space, demand assumption fails, channel converts below X%, the competitive response is faster than expected.) A strategy that only describes success is untested.
- Trace each major move to the founding bet. Every strategic initiative gets a one-line link to why it serves the thesis. A move that serves no part of the founding bet is either defensive maneuvering (which is a separate bet) or scope drift wearing a strategic face.
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 · 87 lines · 74 tokens per session scan A 9df3b14df8e6
helm-strategy-architect is a skill published in the GitHub repository sykoramade/helm-skill (6 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 1,201 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…