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/SyloRei/claude-godmodeWrote 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/sylorei/claude-godmode/changelog)<a href="https://agentmods.dev/commands/sylorei/claude-godmode/changelog"><img src="https://agentmods.dev/badge/commands/sylorei/claude-godmode/changelog/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/sylorei/claude-godmode/changelog"><img src="https://agentmods.dev/badge/commands/sylorei/claude-godmode/changelog.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.00041 | $0.00717 |
| Opus 5 | $0.00020 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
changelog 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 9d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/changelog — draft a changelog entry
Generate a Keep a Changelog–style entry from the commits and diff since the last release tag. A reactive helper — it does not spawn agents and is not part of the spine.
This is a standalone helper for ad-hoc changelog drafting. It does not replace the release-time changelog step
/shipperforms as part of shipping a version — use/shipwhen you are actually cutting a release.
The Job
- Find the last tag.
- Read commits and diff since it.
- Group changes into Added / Changed / Fixed / Removed.
1. Find the range
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -n "$LAST_TAG" ]; then
RANGE="$LAST_TAG..HEAD" # changes since the last release
else
ROOT=$(git rev-list --max-parents=0 HEAD | head -1)
RANGE="$ROOT..HEAD" # no tag yet — whole history
fi
git log --oneline "$RANGE"
git diff --stat "$RANGE"
When there is no tag yet, RANGE spans the root commit to HEAD, so both
commands cover the whole history (never the uncommitted working tree).
2. Group the changes
Classify each meaningful change into one of the four categories. Derive the category from the commit type/intent, not the literal word:
- Added — new features, commands, or capabilities.
- Changed — behavior or interface changes to existing features.
- Fixed — bug fixes.
- Removed — deleted features, deprecations carried out.
Drop noise (merge commits, formatting-only churn, internal refactors with no user-visible effect).
3. Emit the entry
## [Unreleased]
### Added
- …
### Changed
- …
### Fixed
- …
### Removed
- …
Omit any category with no entries. Phrase each line from the user's point of
view, present tense, terse. Print the entry for the user to paste into
CHANGELOG.md.
Output
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.
- 9d ago First seen · 98 lines · 41 tokens per session scan A 5e72238740e0
changelog is a command published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 717 once invoked, about $0.0002 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
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
release
Prepare a release of the sonu plugin — decide the semver bump, sync the version and plugin description across all five homes, run /validate, then hand to /sonu:ship. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
release
Guided release for the skill-engine repo. Bumps the six version surfaces, drafts the CHANGELOG entry, runs validators, then pauses for the maintainer to commit, push, and tag manually. Accepts major / minor / patch / explicit X.Y.Z.
ship
Complete PR workflow from commit to production with validation.
justone-publish
Publish a completed JustOne build — create a public GitHub repo, push, and register on the gallery.
workweek-complete
Weekly release ceremony — validate, docs, release notes, merge.