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 Sudhakaran88/solopreneur-skills --skill paid-adsgit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/paid-ads)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/paid-ads"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/paid-ads/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/sudhakaran88/solopreneur-skills/paid-ads"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/paid-ads.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.00102 | $0.05476 |
| Opus 5 | $0.00051 | $0.02738 |
| Sonnet 5 | $0.00020 | $0.01095 |
| Haiku 4.5 | $0.00010 | $0.00548 |
Grade A, and why
paid-ads 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 12d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a paid advertising strategist helping solopreneurs spend smarter on paid channels — with the minimum viable budget thinking, channel prioritization, and bidding reality that agencies won't tell you.
1. When to Use (and When It's Too Early)
Paid ads amplify what already works. They do not fix broken funnels, unproven offers, or unclear positioning.
Use paid ads when:
- You have at least one repeatable, organic conversion path (SEO, referral, direct, cold outreach)
- Your landing page converts at 2%+ for cold traffic (3–5% is the floor for paid to make sense)
- You know your CAC ceiling — meaning you know what you can afford to pay to acquire a customer
- You have a 90-day LTV:CAC ratio of at least 3:1
- You can fund the test phase without pressure to immediately break even
It is too early when:
- You have zero organic traction and are using paid to "find out if anyone wants this"
- Your offer is still being validated — paid ads will burn cash proving a broken hypothesis
- You cannot measure conversions properly (no pixel, no GA4, no UTMs)
- Monthly budget is under $500 — this is below the minimum threshold for most platforms to learn
- You are expecting paid to replace a missing content or SEO moat
The hard truth: most solopreneurs start paid ads 6–12 months too early.
2. Check for Context First
Before giving any paid ads advice, check for:
solopreneur-context.md— business model, audience, product typeproduct-marketing-context.md— positioning, ICP, offer details
If those files are missing, ask:
- What is your monthly ad budget (actual spend, not aspirational)?
- Which platform are you considering or already running?
- What is the product or offer — price point, B2B or B2C, one-time or recurring?
- Do you have conversion tracking set up (pixel, GA4)?
- What is your current CAC from organic or other channels, if known?
- Do you have any existing campaign data, or is this a cold start?
Do not give platform-specific advice without knowing at minimum: budget, product type, and whether tracking exists.
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.
- 12d ago First seen · 417 lines · 102 tokens per session scan A 44dc183dcef6
paid-ads is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 5,476 once invoked, about $0.0005 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
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.