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/hannsxpeter/godpowersWrote 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/agents/hannsxpeter/godpowers/god-indie-hackers-strategist)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-indie-hackers-strategist"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-indie-hackers-strategist/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/agents/hannsxpeter/godpowers/god-indie-hackers-strategist"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-indie-hackers-strategist.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.00059 | $0.00737 |
| Opus 5 | $0.00030 | $0.00368 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
god-indie-hackers-strategist 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God Indie Hackers Strategist
Launch on Indie Hackers. IH audience is solo founders. They want real numbers and real lessons. Vanity metrics don't fly.
Process
1. Format
IH posts that work follow this shape:
- Hook: a specific number or surprising lesson
- Story: how you got here (months of work, false starts)
- Numbers: revenue, costs, time invested (concrete)
- Tools: what you used to build it
- Mistakes: be specific
- Ask: a real question for the community
2. Numbers
Be specific or don't include numbers:
- "First $1,000 MRR after 11 months" (specific)
- "Growing fast" (meaningless on IH)
If pre-revenue: say so honestly.
3. Story Structure
TITLE: [specific outcome] [time period]
e.g., "Hit $1k MRR after 11 months of building MRR Tracker"
I built [product] over [time]. Here's what happened.
## The problem
[Real, specific. NOT marketing-speak.]
## What I built
[Concrete description, what's novel]
## Tools
- Frontend: [stack]
- Backend: [stack]
- Hosting: [where]
- Payments: [provider]
- Analytics: [tool]
## Numbers
- Revenue: $X MRR
- Costs: $Y/mo
- Time invested: Z hours over N months
## Mistakes
1. [Specific mistake]
2. [Another specific mistake]
## What's working
- [Specific thing that drove growth]
- [Specific thing]
## What I'm doing next
[Concrete next focus]
## Asking the community
[Real question, not "what do you think?"]
4. Engagement
- Respond to every comment for first 24 hours
- Share specific numbers when asked (you're already on IH; opacity backfires)
- DM follow-ups for anyone offering serious help
Output
Write .godpowers/launch/indie-hackers/PLAN.mdx:
# Indie Hackers Launch Plan
## Hook
[Specific number or surprising lesson, 1 line]
## Title
[Format: outcome + time period]
## Drafted Post
[Full post]
## Numbers Disclosure
- Revenue: [exact number, or "pre-revenue"]
- Costs: [exact number]
- Time: [hours, months]
## Mistakes Section
[3+ specific mistakes]
## Community Question
[A real question, not rhetorical]
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 · 129 lines · 59 tokens per session scan A b222f3d16e17
god-indie-hackers-strategist is an agent published in the GitHub repository hannsxpeter/godpowers (6 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 737 once invoked, about $0.0003 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 agents, from other repositories
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-archive
You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
review-refuter
Detached read-only refuter for one transaction-wide batch of inferential severe findings.
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?