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 krillinai/growth-skills --skill growth-diagnosisgit clone --depth 1 https://github.com/krillinai/growth-skillsWrote 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/krillinai/growth-skills/growth-diagnosis)<a href="https://agentmods.dev/skills/krillinai/growth-skills/growth-diagnosis"><img src="https://agentmods.dev/badge/skills/krillinai/growth-skills/growth-diagnosis/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/krillinai/growth-skills/growth-diagnosis"><img src="https://agentmods.dev/badge/skills/krillinai/growth-skills/growth-diagnosis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.02533 |
| Opus 5 | $0.00016 | $0.01267 |
| Sonnet 5 | $0.00006 | $0.00507 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
growth-diagnosis 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 12d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Diagnosis
Maintain Growth Context
At the start, read .agents/growth-context.md when it exists and apply context-contract.md. Reuse compatible product, customer, market, outcome, evidence, and routing facts instead of asking for them again, but surface stale definitions, dates, conflicts, and missing evidence. The file never grants system access or execution authority.
After completing a final diagnosis, create or replace .agents/growth-context.md using growth-context-template.md. Keep it semantically aligned with the canonical diagnosis, exclude credentials and unnecessary personal or row-level data, and do not produce a final-looking context file during triage.
Integrated Capabilities
This Skill consolidates adjacent workflows behind one trigger. Use the main workflow for core requests. When a request matches a module below, read that module before executing it:
Turn a growth symptom into one evidence-backed primary constraint, a 30-day decision plan, and an explicit execution route. Diagnose before prescribing tactics.
Read The Contract
Read evidence-and-routing.md before classifying evidence, setting confidence, working with private inputs, diagnosing China, or choosing an execution route. Read core-read-only-tools.md before using GA4, PostHog, Search Console, HubSpot, Google Ads, or Meta Ads.
Read output-contract.md before producing final JSON or Markdown. Read context-contract.md before reading or writing .agents/growth-context.md. Use protocol.schema.json unchanged as the canonical machine-readable contract. Use playbook-sources.md to cite the relevant Growth Playbook chapter by title and source text.
What ships with it
27 files 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.
- agents/openai.yaml 222 B
- assets/growth-context-template.md 1.6 KB
- assets/protocol.schema.json 7.3 KB
- evals/evals.json 150 KB
- references/context-contract.md 2.9 KB
- references/core-read-only-tools.md 2.7 KB
- references/evidence-and-routing.md 8.1 KB
- references/modules/funnel-analysis/references/analysis-methods.md 4.9 KB
- references/modules/funnel-analysis/references/diagnosis-and-design.md 4.6 KB
- references/modules/funnel-analysis/references/funnel-contract.md 5.2 KB
- references/modules/funnel-analysis/references/playbook-sources.md 1.1 KB
- references/modules/funnel-analysis/SKILL.md 8.6 KB
- references/modules/growth-anomaly-investigation/references/anomaly-contract.md 4.6 KB
- references/modules/growth-anomaly-investigation/references/governance-market-transfer-and-actions.md 4.9 KB
- references/modules/growth-anomaly-investigation/references/integrity-and-decomposition.md 5.3 KB
- references/modules/growth-anomaly-investigation/references/output-contract.md 4.6 KB
- references/modules/growth-anomaly-investigation/references/playbook-sources.md 1.8 KB
- references/modules/growth-anomaly-investigation/references/timeline-mechanisms-and-evidence.md 5.0 KB
- references/modules/growth-anomaly-investigation/SKILL.md 12 KB
- references/modules/growth-maturity-assessment/references/capability-contract-and-evidence.md 5.5 KB
- references/modules/growth-maturity-assessment/references/dependencies-priorities-and-governance.md 5.1 KB
- references/modules/growth-maturity-assessment/references/domains-states-and-assessment.md 5.4 KB
- references/modules/growth-maturity-assessment/references/output-contract.md 4.6 KB
- references/modules/growth-maturity-assessment/references/playbook-sources.md 1.9 KB
- references/modules/growth-maturity-assessment/SKILL.md 11 KB
- references/output-contract.md 6.0 KB
- references/playbook-sources.md 2.1 KB
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.
- 12d ago First seen · 143 lines · 32 tokens per session scan A 7eb4d9241cd6
growth-diagnosis is a skill published in the GitHub repository krillinai/growth-skills (43 stars, last pushed 16d ago), licensed MIT. It adds 32 tokens to every session and 2,533 once invoked, about $0.0002 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 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…