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.
git clone --depth 1 https://github.com/kubachour/mobile-growth-mcpWrote 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/rules/kubachour/mobile-growth-mcp/project-overview)<a href="https://agentmods.dev/rules/kubachour/mobile-growth-mcp/project-overview"><img src="https://agentmods.dev/badge/rules/kubachour/mobile-growth-mcp/project-overview/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/rules/kubachour/mobile-growth-mcp/project-overview"><img src="https://agentmods.dev/badge/rules/kubachour/mobile-growth-mcp/project-overview.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.00682 | $0.00682 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
project-overview 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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Growth MCP — Project Overview
A curated knowledge base of mobile advertising insights + direct Meta Marketing API integration, served via MCP server. Focused on subscription apps and user acquisition across Meta, Google, and TikTok.
Architecture
Three knowledge layers, all accessed via MCP server:
| Layer | What | Retrieval |
|---|---|---|
| What Works | Industry best practices | Hybrid RAG via search_insights |
| What Happened | Past audits, baselines | SQL via account_audits table |
| What Is | Live campaign data | Meta Marketing API via get_meta_* tools |
MCP Tools Available
Knowledge Base
search_insights— semantic + keyword hybrid search (query, topics, applies_to, limit)list_insights— browse all insights with optional filteringget_insight— full content by ID or slug (e.g. "mb-li-001")
Meta Marketing API (requires META_ACCESS_TOKEN)
get_meta_campaigns— list campaigns (defaults: active, last_7d, lean fields)get_meta_adsets— list ad sets, optionally scoped to campaignget_meta_ads— list ads, optionally scoped to ad setget_meta_insights— performance data with breakdowns, levels, date rangesget_meta_ad_fatigue— built-in creative fatigue detection report
MCP Prompts (Reports)
ad-fatigue-report— detect creative fatigue with daily granularityweekly-performance— week-over-week health with Kast diagnostic frameworkcreative-performance— categorize ads by health statusplacement-efficiency— identify placement wasteaudience-composition— age × gender heatmaparchitecture-review— campaign structure evaluationaudit-meta-account— comprehensive account auditcampaign-comparison— side-by-side campaign comparisonplacement-audit— detailed placement auditattribution-analysis— conversion quality validation
Key Conventions
- All Meta tools default to
last_7d,ACTIVEonly, minimal fields (rate limit safety) - No auto-pagination — first page + cursor returned
- Conversion event defaults to
mobile_app_install, configurable per call - Reports reference specific knowledge base insight IDs (e.g. wk-tw-001, mb-li-002)
- Insight slugs follow
{author_initials}-{source_code}-{NNN}pattern
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.
- 8d ago First seen · 73 lines · 682 tokens per session scan A c3801b604211
project-overview is a cursor rule published in the GitHub repository kubachour/mobile-growth-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 682 tokens to every session, about $0.0034 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 cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
performance-optimization
// Use weak/unowned references appropriately class ViewController: UIViewController { private var timer: Timer?
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.