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 peterod99/consultant-skills --skill solo-scaling-without-hiringgit clone --depth 1 https://github.com/peterod99/consultant-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/peterod99/consultant-skills/solo-scaling-without-hiring)<a href="https://agentmods.dev/skills/peterod99/consultant-skills/solo-scaling-without-hiring"><img src="https://agentmods.dev/badge/skills/peterod99/consultant-skills/solo-scaling-without-hiring/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/peterod99/consultant-skills/solo-scaling-without-hiring"><img src="https://agentmods.dev/badge/skills/peterod99/consultant-skills/solo-scaling-without-hiring.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.00043 | $0.01614 |
| Opus 5.5 | $0.00017 | $0.00646 |
| Sonnet 5.5 | $0.00009 | $0.00323 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
solo-scaling-without-hiring 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 2mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solo Scaling Without Hiring
When to use
You've built a profitable solo service business, but you're hitting a ceiling: you can't take on more clients without burning out, and hiring staff feels premature or too expensive. This system lets you 3–5x revenue in 2–3 years without onboarding W2 employees. Implement this phase by phase; each phase funds the next.
The framework
- Productize your service first. Identify the 80/20: the repeatable, high-margin core of your service that 70%+ of clients need. Package it as a fixed offering (not hourly). Example: A positioning consultant's core is a 3-day offsite + 30-day implementation support = $25k fixed. Productization lets you quote faster, deliver predictably, and scale delivery.
- Systematize your delivery. Document the steps, templates, decision trees, and quality gates for your core offering. You're not trying to delegate yet: you're building the repeatable machine you'll eventually hand off. A playbook is leverage; gut-feel delivery is a bottleneck.
- Hire a fractional VA or contractor for non-core work. First hire is NOT a delivery person; it's an operations person. Someone who schedules, invoices, manages email, tracks projects, and handles admin. Pay them 20–30 hours/week ($500–1,500/month). This frees your highest-value time for client work and business development.
- Layer in strategic partnerships or referral finders. Before hiring a full-time salesperson, create referral partnerships or hire someone part-time to cultivate warm referrals (not cold outreach). Referrals close 3–5x faster and convert better. Example: A B2B consultant pays a referral partner 20% commission on deals they source: no fixed salary.
- Add a delivery contractor or operations contractor. Once your productized service is humming and you have a 6-month waitlist, hire a fractional contractor (50% of a full-time employee's salary) to handle 40% of delivery or operations. They work 20 hours/week on your defined processes. You keep 60–70% of their billing rate; they take home competitive pay without benefits overhead.
- Only then consider scaling to team revenue. After productization, systematization, and 2–3 contractors, you've built repeatable business. Then you can hire a full-time person (salesperson, operations lead, or second delivery person). You've proven the model can scale without you in every decision. Team revenue (adding W2s) happens in Phase 3, after solo leverage is maxed out.
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.
- 2mo ago First seen · 45 lines · 0 tokens per session scan A 00b7228abe20
solo-scaling-without-hiring is a skill published in the GitHub repository peterod99/consultant-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,614 once invoked, about $0.0002 per session on Opus 5.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
good-morning
Daily morning briefing that pulls calendar, tasks, pipeline, and outreach data into one view.
good-night
End-of-day review that summarizes accomplishments, drafts EOD message, previews tomorrow, and optionally syncs call recordings.
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…