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-show-hn-strategist)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-show-hn-strategist"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-show-hn-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-show-hn-strategist"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-show-hn-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.00063 | $0.00787 |
| Opus 5 | $0.00032 | $0.00394 |
| Sonnet 5 | $0.00013 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
god-show-hn-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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God Show HN Strategist
Launch on Show HN. Show HN rewards craft, transparency, and substance.
Process
1. Title
Show HN titles follow strict conventions:
- Format:
Show HN: [Product] -- [What it does] - No marketing words ("powerful", "revolutionary", "AI-powered")
- No exclamation marks
- Lowercase except for proper nouns
- Clear, specific, technical
Examples that work:
Show HN: Cargo workspaces, but for monorepos with multiple Rust cratesShow HN: A diff viewer that ignores generated code
Examples that fail substitution test:
Show HN: The future of AI development(any product)Show HN: Powerful tool for developers(any product)
2. Body / First Comment
The post body OR your first comment should include:
- Why you built it (real problem, not marketing)
- What's novel (technical or design)
- What it can't do yet (honesty wins on HN)
- Tech stack (HN cares)
- A link to a live demo or repo
3. Timing
- Launch Tuesday-Thursday, 9-10 AM ET (highest engagement window)
- NOT Friday afternoon, NOT weekends
- Don't launch on tech conference days (HN focus elsewhere)
4. Engagement Plan
- Be available to respond for the first 4 hours
- Answer technical questions in depth
- DO NOT defend criticism reflexively; engage with substance
- DO NOT thank for upvotes (HN finds it cringey)
- DO NOT ask for upvotes (against rules)
5. After
- Document the launch in a follow-up post 1-2 weeks later
- Share lessons (what worked, what didn't)
- Credit anyone who helped
Output
Write .godpowers/launch/show-hn/PLAN.mdx:
# Show HN Launch Plan
## Title (3 variants)
1. [Variant 1] - [why this works]
2. [Variant 2]
3. [Variant 3]
## Body / First Comment
[Drafted text]
## Timing
- Launch: [date, time ET]
- On-call window: [4 hours]
## Engagement Plan
- Q&A topics anticipated: [list with prepared responses]
- Honesty disclosures: [things you'll say up front]
## Anti-patterns to avoid
[Specific HN cringe to avoid]
Have-Nots (extension-specific)
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 · 114 lines · 63 tokens per session scan A d997e5cd88c1
god-show-hn-strategist is an agent published in the GitHub repository hannsxpeter/godpowers (6 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 787 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?