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-oss-release-strategist)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-oss-release-strategist"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-oss-release-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-oss-release-strategist"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-oss-release-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.00064 | $0.00838 |
| Opus 5 | $0.00032 | $0.00419 |
| Sonnet 5 | $0.00013 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
god-oss-release-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 10d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God OSS Release Strategist
Release an open source library. The library succeeds or fails on its README, versioning discipline, and community signals.
Process
1. README
Required sections (in order):
- What it is - one sentence, substitution-tested
- Why it exists - what existing libraries don't do
- Install - copy-pasteable, one command
- Quick start - 5-10 lines of code that work
- Documentation - link to full docs
- License - one line + link
- Status - is this production-ready, alpha, or experimental?
2. Versioning
- Start at v0.1.0 (NOT v1.0)
- v0.x.y: API can change between minors
- v1.0: stable API, breaking changes only in v2.0
- Commit to SemVer publicly
- Document deprecations in CHANGELOG
3. Examples
Every example in the README MUST run. Every example in docs MUST run. Run them as part of CI.
If an example uses dummy data, use realistic dummy data (not "foo"/"bar").
4. Status Signals
These signal a library is alive:
- Recent commits (within last 90 days)
- CHANGELOG entries
- Closed issues
- Released versions
These signal a library is dead:
- Last commit >1 year ago
- Stale issues with no response
- README says "TODO: write docs"
5. Launch
OSS launches well when:
- Posted on Show HN (if developer-facing): use /god-show-hn
- Posted on Reddit r/programming or relevant subreddit
- Tweet thread from your account
- Submission to relevant newsletters (e.g., This Week in )
Don't:
- Spam Twitter looking for followers
- Post to multiple subreddits in same hour (cross-posting flag)
- Solicit GitHub stars
Output
Write .godpowers/launch/oss/PLAN.mdx:
# OSS Release Plan
## Library Name
[name]
## README Status
- [ ] What it is (substitution-tested)
- [ ] Why it exists
- [ ] Install command (verified runs)
- [ ] Quick start (verified runs)
- [ ] Documentation link
- [ ] License + link
- [ ] Status (production / alpha / experimental)
## Version
Releasing as: v0.1.0
Stability promise: API may change between v0.x; v1.0 will freeze.
## Examples
All [N] code examples in README and docs verified to run.
## Launch Channels
- Show HN: /god-show-hn workflow
- Reddit: [subreddit]
- Twitter: [thread plan]
- Newsletter: [if applicable]
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.
- 10d ago First seen · 126 lines · 64 tokens per session scan A b78a24afa33d
god-oss-release-strategist is an agent published in the GitHub repository hannsxpeter/godpowers (6 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 838 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
ijfw-dep-audit
Flag publishConfig drift, lock-in version skew, dep version mismatches. Trigger before any release wave.
ijfw-doc-writer
Writes/updates CHANGELOG.md + README.md from commit log + handoff. Trigger before ship-gate.
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
release-auditor
Internal dynos-work agent. Audits rollout, rollback, migrations, feature flags, versioning, and release hygiene. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
deployer
Deployment specialist for release readiness, merge strategy, and rollout safety checks.