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 saski/arnesto --skill growth-loopsgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/growth-loops)<a href="https://agentmods.dev/skills/saski/arnesto/growth-loops"><img src="https://agentmods.dev/badge/skills/saski/arnesto/growth-loops.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.00086 | $0.00584 |
| Opus 5 | $0.00043 | $0.00292 |
| Sonnet 5 | $0.00017 | $0.00117 |
| Haiku 4.5 | $0.00009 | $0.00058 |
Grade A, and why
growth-loops 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 5d 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.
This is a copy
100% identical to growth-loops — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Growth Loops
What It Is
Growth Loops is a framework for building sustainable, compounding growth. The core insight: the best growth systems are loops, not funnels — where the output of one cycle becomes the input for the next.
Traditional growth thinking focuses on funnels: acquire users at the top, optimize conversion through stages, and measure output at the bottom. But funnels are linear. You pour effort in, you get results out, and then you start over. Loops are different: each cycle generates the fuel for the next cycle.
The key shift: Move from asking "How do we get more users?" to asking "How does each user we acquire generate more users?"
When to Use It
Use Growth Loops when you need to:
- Design your core growth engine before or after product-market fit
- Move beyond paid acquisition to more sustainable growth
- Understand why growth isn't compounding despite acquisition efforts
- Build virality, content, or sales loops into your product
- Evaluate distribution strategies for a new product or feature
- Diagnose why your "growth team" isn't producing results
- Plan how to capitalize on new distribution platforms (like ChatGPT)
When Not to Use It
- You haven't validated that anyone wants your product (find PMF first)
- You're optimizing micro-conversions without a growth model
- You're looking for "growth hacks" rather than systematic growth
- Your product has no natural mechanism for users to generate more users
Resources
Reforge Programs:
- Growth Series — the comprehensive deep dive
- Product-Led Growth course — PLG and PLS specifics
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.
- 5d ago First seen · 61 lines · 86 tokens per session scan A 295f565d867f
growth-loops is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 2d ago), licensed Unlicense. It adds 86 tokens to every session and 584 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to growth-loops, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.