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.
/plugin marketplace add godshiba/genesisnpx agentmods add plugins/godshiba/genesis/genesis-usagegit clone --depth 1 https://github.com/godshiba/genesisGrade 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 yesterday.
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 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.
- yesterday First seen · 14 lines scan A 2ef1c7d40be3
genesis-usage is a plugin published in the GitHub repository godshiba/genesis (2 stars, last pushed 2mo 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
qiushi-skill
Qiushi Skill: methodology skills for AI agents guided by seeking truth from facts, with Claude Code, Cursor, OpenClaw, Codex, OpenCode, and Hermes guidance.
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
bengous-plugins
Personal Claude Code plugins: git workflows, code quality, agent orchestration, and plugin tooling.
phd-deepread-workflow
Transform academic PDFs into structured literature notes and critical-thinking canvases for Obsidian.