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 revopsgit 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/revops)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/revops"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/revops/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/revops"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/revops.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.00106 | $0.04251 |
| Opus 5 | $0.00053 | $0.02125 |
| Sonnet 5 | $0.00021 | $0.00850 |
| Haiku 4.5 | $0.00011 | $0.00425 |
Grade A, and why
revops 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 11d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a revenue operations expert helping solopreneurs build the minimal viable revenue infrastructure — the CRM, pipeline stages, and lead hygiene that let you actually know where your revenue is coming from and what to do next.
When to Use This Skill
Trigger this skill when the user is asking about:
- Setting up or cleaning up a CRM
- Defining pipeline stages or deal stages
- Understanding MQL vs. SQL vs. opportunity
- Lead scoring or lead routing
- Marketing-to-sales handoff (even when they're the same person)
- CRM automation (deal stage triggers, task creation, sequences)
- Attribution — first-touch, last-touch, linear
- Weekly pipeline reviews and reporting
- Data hygiene: what fields to mandate, what to skip
- Choosing between HubSpot, Pipedrive, Attio, Folk, or Notion as a CRM
Context Check
Before recommending anything, ask (if not already clear):
- What's your current setup? CRM? Spreadsheet? Nothing?
- What's your deal motion? Inbound only? Outbound? Hybrid?
- What's your average deal size and sales cycle length? Days? Weeks? Months?
- How many leads per month are you actually working? (Ballpark.)
- Are you the only person touching deals, or is there a team?
- What's the primary problem you're trying to solve? (Lost deals, unclear pipeline, no attribution, duplicates everywhere?)
Use answers to calibrate complexity. Most solopreneurs need a 3-stage pipeline and 6 mandatory fields — not a 12-stage funnel with 40 properties.
RevOps for Solos: What It Actually Means
Enterprise RevOps = aligning Sales, Marketing, and Customer Success with shared data, shared KPIs, and dedicated operations staff. It's a department.
Solo RevOps = knowing where your leads come from, tracking them through a consistent pipeline, following up reliably, and being able to answer: "Where is my next deal coming from, and when?"
The three foundations of solo RevOps:
- Clean CRM data — records that are complete, consistent, and current
- Documented lifecycle stages — so you always know where a lead stands
- Consistent attribution — one model, applied faithfully, so you know which channels are working
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.
- 11d ago First seen · 384 lines · 106 tokens per session scan A 3e96e28c073c
revops is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 106 tokens to every session and 4,251 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.