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/godshiba/genesisWrote 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/plugins/godshiba/genesis/genesis-usage)<a href="https://agentmods.dev/plugins/godshiba/genesis/genesis-usage"><img src="https://agentmods.dev/badge/plugins/godshiba/genesis/genesis-usage/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/plugins/godshiba/genesis/genesis-usage"><img src="https://agentmods.dev/badge/plugins/godshiba/genesis/genesis-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
genesis-usage 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 1mo 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.
What it actually says
{
"name": "genesis-usage",
"displayName": "GENESIS Usage Sensor",
"version": "1.2.0",
"description": "A usage sensor, not a HUD. Claude Code exposes subscriber rate_limits (5-hour and 7-day) to the statusline, so the statusline feeds them to a Stop-hook sensor that, when you near a cap with a reset still far off, recommends or auto-triggers /genesis:close - a clean handoff instead of a hard cutoff. Optional mid-turn watch catches a crossing between tool calls in a big turn. The one-line statusline readout is the required data feed. Fails open for API users.",
"author": {
"name": "godshiba",
"url": "https://github.com/godshiba"
},
"repository": "https://github.com/godshiba/genesis",
"license": "MIT",
"keywords": ["usage", "rate-limits", "session-continuity", "statusline", "sensor"]
}
What it installs
The manifest is a name and a version. 1 skill, 2 hooks travel with it, and installing the plugin installs all of them — 81 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 14 lines scan A 2ef1c7d40be3
genesis-usage is a plugin published in the GitHub repository godshiba/genesis (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
workinggenius
A development workflow that walks every piece of work through the six Working Geniuses — Wonder, Invention, Discernment, Galvanizing, Enablement, Tenacity — every stage a command the user types, every checkpoint a live exchange.
duet
Claude Code plugin for reflection, code quality, writing, and design.
ponytail
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.
dev-skills
Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents.
handbook
Core Claude Code handbook with best practices and essential tools.
hush
Quieter sessions for Claude Code: less narration, shorter tool output and concise answers focused on the result.