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 nocodework/growth-os --skill connectgit clone --depth 1 https://github.com/nocodework/growth-osWrote 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/nocodework/growth-os/connect)<a href="https://agentmods.dev/skills/nocodework/growth-os/connect"><img src="https://agentmods.dev/badge/skills/nocodework/growth-os/connect/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/nocodework/growth-os/connect"><img src="https://agentmods.dev/badge/skills/nocodework/growth-os/connect.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.00122 | $0.01393 |
| Opus 5 | $0.00061 | $0.00696 |
| Sonnet 5 | $0.00024 | $0.00279 |
| Haiku 4.5 | $0.00012 | $0.00139 |
Grade A, and why
connect 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
connect
The integration wizard. Connecting analytics and ad accounts is where most tools lose people — the approval flows are confusing, some take weeks, and it's never clear what you can start right now. connect fixes that by telling you exactly what's fast, what's slow, and walking you through each one in the right order.
What it does
- Detects which credentials are already present in
.envand which sources are live. - Classifies every source as 🟢 (zero-approval, minutes) or 🔴 (needs an owner-side approval with real lead time).
- Sequences the setup so the user gets value today: do all the 🟢 sources now, kick off the 🔴 approvals in parallel so their clock starts.
- Guides each connection step by step, linking to the matching
docs/integrations/*page. - Separates the two very different kinds of approval so nobody waits on the wrong thing.
The two kinds of approval — this is the key distinction
- Developer approval (once, ever). A one-time setup the account owner does at the platform level — a developer token, a verified business, an app that passes review. Slow, but you do it once and it's done for the whole org. These are the 🔴 sources.
- User OAuth (per person, fast). An individual granting read access to their own data via a consent screen. Seconds to minutes. These are the 🟢 sources (plus, later, the read grant on the 🔴 platforms once the developer approval exists).
Conflating these is why integrations feel painful. connect keeps them apart and tells the user which clock they're on.
The sources
🟢 Zero-approval — start now, minutes each
- GA4 (Data API) — service-account JSON added to the property, or OAuth with
analytics.readonly. →docs/integrations/ga4.md - Google Search Console —
webmasters.readonly, the same service account added as a user on the property. →docs/integrations/gsc.md - MailerLite — Bearer API key generated in the MailerLite UI. →
docs/integrations/mailerlite.md - PageSpeed Insights — an API key from a Google Cloud project. →
docs/integrations/pagespeed.md
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 · 66 lines · 122 tokens per session scan A dfd1857421db
connect is a skill published in the GitHub repository nocodework/growth-os (6 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 1,393 once invoked, about $0.0006 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
gtm-reverse-engineer
Reverse-engineer any company's public go-to-market into an evidence-graded, multi-file playbook (copy / adapt / skip). Use whenever the user wants competitor GTM teardown, growth forensics, channel analysis (Instagram, X/Twitter, LinkedIn, ads, Reddit/community, SEO, jobs, pricing), "how did X grow", unicorn/breakout…
content-planner
GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
setup-cms
Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my…
newsletter-monetization-planner
Use when the user asks to "monetize my newsletter", "build a sponsorship rate card", or "model paid-subscription revenue"; produces a revenue model (paid tiers, ad/sponsorship inventory + CPM/flat rate card, referral/boost loops), a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D…
audience-mapper
Use when the user asks to "analyze my target audience", "build an audience profile for influencer targeting", "research a niche community", or "deep-dive a subculture before partnering with creators"; in audience mode produces demographic/psychographic profiles, a platform-priority matrix, named personas, and an…