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 agentmods add skills/jeff-kazzee/growth-engine/growth-setupnpx skills add Jeff-Kazzee/growth-engine --skill growth-setupgit clone --depth 1 https://github.com/Jeff-Kazzee/growth-engineWrote 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/jeff-kazzee/growth-engine/growth-setup)<a href="https://agentmods.dev/skills/jeff-kazzee/growth-engine/growth-setup"><img src="https://agentmods.dev/badge/skills/jeff-kazzee/growth-engine/growth-setup.svg" alt="Measured on agentmods" 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.00062 | $0.00519 |
| Opus 5 | $0.00031 | $0.00260 |
| Sonnet 5 | $0.00012 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
growth-setup 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Setup
Create (or refresh) the persistent state that powers every Growth Engine skill: a growth-engine/ folder in the user's workspace containing their builder profile and memory files.
Procedure
1. Check for existing state
Look for growth-engine/ at the workspace root. If it exists, read profile.md and switch to update mode: confirm what's stale, interview only for gaps, and preserve history.
2. Interview the user
Run the interview in references/interview-guide.md. It must establish three things above all: who the user is, what they want their branding to be, and what they want to stand out as — plus goals, constraints, tone, and anti-positioning. This works for any user: developer, writer, artist, freelancer, shop owner.
3. Enrich with research
Don't make the user type what can be discovered, and verify what they claimed:
- If they shared public links (GitHub, Substack, X/Twitter, Bluesky, LinkedIn, personal site, storefront), fetch and read them.
- With permission, search the user's workspace/notes for goals, projects, skills, and existing brand or research material. If the workspace has a navigation index (e.g., a knowledge graph or MOC files), use it instead of crawling everything.
- Mark every profile item stated, found (with source), or inferred (needs confirmation).
4. Write the state folder
Create the files exactly as specified in references/state-schema.md. Present the drafted profile.md to the user for correction before finalizing. Never invent achievements — anything unverified stays marked inferred.
5. Close the loop
Tell the user which skills to run next (typically opportunity-radar or brand-positioning) and offer to schedule a recurring growth-review.
Rules
- Read
growth-engine/playbook.mdfirst if it exists and obey its directives. - Update mode must never delete decision-log history or reviews.
- The profile is the single source of truth other skills read — keep it concise, current, and honest.
What ships with it
2 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.
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 · 41 lines · 62 tokens per session scan A 638aecfd12bd
growth-setup is a skill published in the GitHub repository Jeff-Kazzee/growth-engine (4 stars, last pushed 6d ago), licensed MIT. It adds 62 tokens to every session and 519 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-08-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…