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 dashboardgit 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/dashboard)<a href="https://agentmods.dev/skills/nocodework/growth-os/dashboard"><img src="https://agentmods.dev/badge/skills/nocodework/growth-os/dashboard/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/dashboard"><img src="https://agentmods.dev/badge/skills/nocodework/growth-os/dashboard.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.00085 | $0.00985 |
| Opus 5 | $0.00043 | $0.00492 |
| Sonnet 5 | $0.00017 | $0.00197 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
dashboard 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dashboard
The read-out. After onboarding, connecting, and auditing, the pieces live in a few places — the hub, .env, the GEO scorecard. dashboard pulls them together into one plain-text report so the user can see, at a glance, where the business stands and what to do next. It composes; it doesn't re-run the heavy work.
What it does
Assembles four things into one overview:
- Live baseline — the current numbers from GA4 and Search Console, if connected: traffic, top pages, top queries, sources, conversions where available.
- Audit findings — the ranked
## Audit Findingsfrom the hub, top items surfaced. - GEO scorecard — the latest
geo-auditmetrics: visibility, rank, sentiment, recommendation rate, share of voice, citation domains. - Integration status — what's connected (🟢), what's pending approval (🔴), and what that unlocks.
Then it closes with the single highest-leverage next action.
When to use
- The user wants the state of play without kicking off a full audit.
- A weekly/monthly check-in on where growth stands.
- Right after
onboardfinishes, as the tidy summary of everything that just happened.
Steps
-
Read the hub. Load
.agents/product-marketing.md— positioning (one-line reminder of who this is for), the## Audit Findingssection, and any stored GEO scorecard. -
Pull a fresh baseline if cheap. If GA4/GSC are connected, run the light read-side commands for current numbers (
growth-os ga4 visitors 30,growth-os ga4 pages 30,growth-os gsc queries 30). These are fast and give the report live data instead of stale audit numbers. If not connected, say so and show the last known state. -
Check integration status. Scan
.env(viaconnect's detection) and list 🟢 live / 🔴 pending, noting what each pending item will unlock when it lands. -
Compose the report. One clean text layout, top to bottom:
- Who — one line: business + ICP.
- Baseline — the live numbers, with the comparison window stated (last 30 days, etc.).
- Top findings — the three-to-five highest-priority audit items, each with its fix owner.
- GEO — the scorecard in a compact block.
- Integrations — the 🟢/🔴 status list.
- Do next — the one action worth taking now.
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 · 61 lines · 85 tokens per session scan A 1e518529947a
dashboard is a skill published in the GitHub repository nocodework/growth-os (6 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 985 once invoked, about $0.0004 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…