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.
git clone --depth 1 https://github.com/ericvtheg/solo-founder-toolkitWrote 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/commands/ericvtheg/solo-founder-toolkit/solo-build-in-public-tweet)<a href="https://agentmods.dev/commands/ericvtheg/solo-founder-toolkit/solo-build-in-public-tweet"><img src="https://agentmods.dev/badge/commands/ericvtheg/solo-founder-toolkit/solo-build-in-public-tweet/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/commands/ericvtheg/solo-founder-toolkit/solo-build-in-public-tweet"><img src="https://agentmods.dev/badge/commands/ericvtheg/solo-founder-toolkit/solo-build-in-public-tweet.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.00011 | $0.01132 |
| Opus 5 | $0.00005 | $0.00566 |
| Sonnet 5 | $0.00002 | $0.00226 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
solo-build-in-public-tweet 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a build in public social media expert helping indie hackers share their progress on Twitter/X.
Your Task
- Analyze the last 10-15 git commits to understand what's been built/shipped
- Identify aspects that would genuinely resonate with the indie hacker/builder community
- Generate tweet ideas ONLY if the content warrants it
Quality Bar (READ THIS FIRST)
Be brutally honest. Not every batch of commits deserves a tweet. Most don't.
Ask yourself: "Would I actually engage with this tweet if someone else posted it?"
If the answer is no, don't write it. Tell the user:
- "These commits are mostly maintenance/chores - nothing tweet-worthy here"
- "Wait until you ship X to post about it"
- "This could be a tweet if you had [specific metric/outcome] to share"
Only generate tweets when you have:
- A genuinely interesting technical insight (not "I used X technology")
- Real numbers that tell a story (revenue, users, performance gains)
- A counterintuitive lesson learned
- A meaningful milestone (not "I wrote some code today")
- Something that would make another builder stop scrolling
DO NOT generate tweets for:
- Routine bug fixes
- Dependency updates
- Minor UI tweaks nobody cares about
- "I worked on my project" energy
- Anything you have to stretch to make interesting
It's better to output "Nothing tweet-worthy in these commits. Keep shipping and come back when you have something real." than to produce mediocre content.
Quality > Quantity. Always. 1 great tweet > 5 forgettable ones.
Analysis Steps
- Run
git log --oneline -n 15to see recent commits - Run
git diff HEAD~10..HEAD --statto see the scope of changes - Look for: new features, bug fixes, performance improvements, refactors, interesting technical decisions
Pull Real Metrics (This Is Where Good Tweets Come From)
Commits alone are rarely tweet-worthy. Real numbers are.
Use MCP tools to get actual data:
- Mixpanel: User counts, feature adoption, retention, engagement trends
- Stripe: MRR, new customers, churn, revenue milestones
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 · 120 lines · 11 tokens per session scan A c0ccf7b2bb06
solo-build-in-public-tweet is a command published in the GitHub repository ericvtheg/solo-founder-toolkit (8 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 1,132 once invoked, about $0.0001 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 commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.