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 assess-growth-vectorsgit 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/assess-growth-vectors)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/assess-growth-vectors"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/assess-growth-vectors/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/assess-growth-vectors"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/assess-growth-vectors.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.00061 | $0.00892 |
| Opus 5.5 | $0.00024 | $0.00357 |
| Sonnet 5.5 | $0.00012 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
assess-growth-vectors 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 2mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess Growth Vectors
When to use
For strategy leads testing whether a portfolio of growth initiatives can realistically hit a stated target — arithmetic most growth plans skip.
What this skill does not do
- Does not run without a growth target — halt and ask.
- Does not take optimistic upside at face value — applies category success-rate priors.
- Does not approve mix shifts — names options; strategist decides.
- Does not invent initiative upside — user-provided or
INPUT NEEDED.
Preconditions
| Input | If missing |
|---|---|
| Growth target (rate, horizon) | Halt — skill meaningless without target |
| Initiative list with stated upside | Ask; partial OK with gaps flagged |
| Practice profile | Read or [PROVISIONAL] |
Provisional mode
No profile: state success-rate priors explicitly as [PROVISIONAL — argue in room]; all upside figures user-sourced.
Trust spine
- Analytical Rigor (mandatory): Category classification honest; priors visible; gap arithmetic explicit.
- Confidence bands (
hypothesis-driven-analysis): High = triangulated priors; Low = assumption-driven — label load-bearing assumptions. - Escalation: Mislabeled adjacent (actually transformational) → push back; gap softened → forbidden.
Workflow
- Read practice profile for growth target and portfolio context.
- Categorize each initiative: core / adjacent / transformational — classify honestly.
- Apply stated success-rate prior per category (visible, arguable).
- Realistic contribution = stated upside × prior; sum portfolio.
- State growth gap: sum vs target in plain terms.
- If gap: name options (more initiatives, lower target, mix shift, extend horizon).
Output format
GROWTH TARGET: [rate] over [horizon]
INITIATIVES:
[Initiative] — [Core | Adjacent | Transformational] — Stated upside: [value] —
Success-rate prior: [X%] — Realistic contribution: [value]
TOTAL REALISTIC CONTRIBUTION: [sum] vs TARGET: [value] — GAP: [amount | none]
IF GAP EXISTS — OPTIONS:
1. [...]
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.
- 2mo ago First seen · 94 lines · 61 tokens per session scan A 04a15e991fcf
assess-growth-vectors is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 892 once invoked, about $0.0002 per session on Opus 5.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.
assess-growth-vectors compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| assess-growth-vectorsdaddia/claude-for-strategy | Skill | 2 | 4mo ago | MIT | A | 61 | Claude Code |
| reviewhelderberto/agent-skills | Skill | 20 | 11d ago | MIT | A | 0 | Claude Code |
| tddhelderberto/agent-skills | Skill | 20 | 11d ago | MIT | A | 71 | Claude Code |
| visual-reviewhelderberto/agent-skills | Skill | 20 | 11d ago | MIT | A | 84 | Claude Code |
| to-prhelderberto/agent-skills | Skill | 20 | 11d ago | MIT | A | 25 | Claude Code |
| to-ticketshelderberto/agent-skills | Skill | 20 | 11d ago | MIT | A | 0 | Claude Code |
| debatehelderberto/agent-skills | Skill | 20 | 11d ago | MIT | A | 28 | Claude Code |