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 daddia/claude-for-strategy --skill tech-strategy-briefgit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/tech-strategy-brief)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/tech-strategy-brief"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/tech-strategy-brief/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/daddia/claude-for-strategy/tech-strategy-brief"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/tech-strategy-brief.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.00058 | $0.00769 |
| Opus 5 | $0.00029 | $0.00385 |
| Sonnet 5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
tech-strategy-brief 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 6d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Strategy Brief
When to use
BLUF decision brief for technology strategy calls — options including do-nothing, recommendation first, explicit ask.
What this skill does not do
- Does not make architecture decisions — draft for ARB/sign-off.
- Does not invent vendor pricing — tag
[verify]orINPUT NEEDED. - Does not skip do-nothing option — always one of the real choices.
Preconditions
| Input | If missing |
|---|---|
| Precise decision statement | Ask to narrow |
| Transformation practice profile | Proceed [PROVISIONAL] on platform vocabulary |
Provisional mode
Without EA principles from profile: flag recommendations [review] against house rules once configured.
Trust spine
Option-evaluation bands; recommendation before detail; conditions that would flip recommendation stated; GATE before board/exec final.
Workflow
- Read practice profile for platform vocabulary and risk posture.
- State decision precisely.
- Lay out options including do-nothing.
- Per option: requirements, cost (time/disruption/lock-in), main risk.
- State recommendation first (BLUF).
- 2–4 MECE reasoning points.
- Explicit ask — sign-off, budget, date.
- Flag what would change the recommendation.
Output format
CONFIDENCE: [defensible recommendation | structured first pass]
RECOMMENDATION: [one to two sentences — stated first]
REASONING:
1. [...]
2. [...]
OPTIONS:
| Option | Requires | Cost | Main risk |
|---|---|---|---|
ASK: [decision needed, by when, from whom]
WOULD FLIP RECOMMENDATION IF: [...]
Worked example
Input: Shared Identity platform vs per-product IdP.
Expected output (excerpt):
RECOMMENDATION: Adopt shared Identity platform — reduces duplicate security review [review]
WOULD FLIP RECOMMENDATION IF: Regulatory separation requires per-BU identity boundary [review]
Quality checks before delivering
- Decision precise, not vague architecture improvement
- Do-nothing option included
- Recommendation before options detail
- Flip conditions stated
- Figures source-tagged
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.
- 6d ago First seen · 100 lines · 58 tokens per session scan A b2016a2e28d0
tech-strategy-brief is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 769 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.