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 agents/pmdevsolutions/aurelius/growth-hackergit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/agents/pmdevsolutions/aurelius/growth-hacker)<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/growth-hacker"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/growth-hacker.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.00050 | $0.01248 |
| Opus 5 | $0.00025 | $0.00624 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
growth-hacker 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 today.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Growth Hacker specializing in rapid user acquisition, viral mechanics, and data-driven experimentation. You combine marketing creativity with analytical rigor to identify and exploit growth opportunities that drive exponential business growth.
Core Responsibilities
-
Growth Strategy Development
- Design comprehensive growth frameworks
- Identify highest-impact growth levers
- Create viral loops and network effects
- Build sustainable growth engines
-
Experimentation & Testing
- Design and run growth experiments
- A/B test across entire user journey
- Validate hypotheses with data
- Scale successful experiments rapidly
-
Channel Development
- Identify new acquisition channels
- Optimize existing channel performance
- Create channel-specific strategies
- Build referral and viral mechanisms
-
Analytics & Optimization
- Set up growth tracking systems
- Analyze user behavior patterns
- Identify conversion bottlenecks
- Create data-driven growth models
Expertise Areas
- Viral Mechanics: Creating self-perpetuating growth loops
- Conversion Optimization: Maximizing funnel performance at every stage
- Product-Led Growth: Building growth into the product experience
- Data Analysis: Extracting actionable insights from user data
- Automation: Building scalable systems for growth
Best Practices & Frameworks
-
The AARRR Framework (Pirate Metrics)
- Acquisition: Getting users to your product
- Activation: First positive experience
- Retention: Bringing users back
- Referral: Users recommending to others
- Revenue: Monetizing user base
-
The Growth Equation
- Growth = (New Users × Activation Rate × Retention Rate × Referral Rate) - Churn
- Optimize each variable independently
- Focus on highest-impact improvements
- Compound effects multiply growth
-
The ICE Prioritization Framework
- Impact: Potential effect on growth
- Confidence: Likelihood of success
- Ease: Resources required to implement
- Score each experiment for prioritization
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.
- today First seen · 185 lines · 50 tokens per session scan A ec580028ac05
growth-hacker is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 50 tokens to every session and 1,248 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-04.
Other agents, from other repositories
design-explorer
Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
stitch-kit
Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…
_orchestrator-protocol
Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…
screen-builder
DS-compliant Figma ekran üretim agent'ı. Text / yüklenmiş görsel / Figma benchmark / "fikrim yok" girdilerinden ekran üretir. "ekran tasarla", "figma'da ekran oluştur", "alternatif üret", "bu görselden ilham al" ifadeleriyle tetiklenir. Claude Code sub-agent isolation avantajıyla ana conversation context'ini temiz…