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.
npx agentmods add skills/godshiba/genesis/setupnpx skills add godshiba/genesis --skill setupgit clone --depth 1 https://github.com/godshiba/genesisWhat 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 | $0.00081 | $0.01848 |
| Opus 5 | $0.00041 | $0.00924 |
| Sonnet 5 | $0.00016 | $0.00370 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade B, and why
setup scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.claude/settings.json` so you never hand-edit JSON or memorize an env var. How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/genesis-usage:setup - Configure the usage sensor
The sensor works out of the box; this makes it yours. It writes choices into
~/.claude/settings.json so you never hand-edit JSON or memorize an env var.
If the user passed a number as an argument (e.g. /genesis-usage:setup 80),
treat it as the 5-hour cap - but still show the weekly cap (default 85) so it is
never set silently. A second number sets the weekly cap too
(/genesis-usage:setup 80 75).
1. Check eligibility first (be honest)
The sensor only fires on Claude.ai Pro/Max (Claude Code v1.0.80+), and
only after the first model response in a session - that is when Claude Code
starts sending rate_limits. On API-key-only accounts it stays silent by
design. If the user is on API keys, say so plainly and stop - configuring it
will not make data appear.
Critical: rate_limits is delivered to the statusline input only, never
to hook input. The sensor is a Stop hook, so it gets its data from a bridge file
the statusline writes each render. The statusline is therefore required, not
optional - without it the sensor has no usage data and never fires. Treat
step 4 as part of the core setup, not an extra.
2. Ask what they want (one short round)
Show every setting's current value (or its default) and let the user keep or change it - never leave a setting at a default the user never saw. Both caps are first-class; present them as a pair:
- 5-hour cap - usage %% that triggers the warning (default 90).
- 7-day (weekly) cap - usage %% that triggers the weekly warning (default 85).
- Mid-turn watch -
on/off(default off). Ask this right after the two caps, because it builds on them. Describe it plainly: the normal sensor only checks at the end of each turn, so a single large multi-tool turn can blow past the cap before it ever fires. Turning this on adds a PostToolUse hook that checks the same usage numbers after every tool call, so a crossing is caught between tools - inadviseit warns you and Claude mid-turn; inenforce(inside a GENESIS project) it writes a snapshot itself and tells Claude to run/genesis:closebefore the next tool. Default off because it runs on a hot path; suggestonto anyone who runs long agentic turns. It reuses the same caps and the once-per-bucket throttle, so it adds no new tuning. - Mode -
advise(warn in the terminal, default),enforce(block the turn so Claude runs/genesis:close), oroff. Note: mid-turn watch follows this same mode. - Desktop notification -
on/off(default off). When on, the sensor also posts a macOS notification, useful when you are working in another app. - Statusline - required data feed (see step 4). Default to installing it; only skip if the user already runs a statusline they will not replace - and warn them the sensor cannot fire without one.
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.
- 2d ago First seen · 141 lines · 81 tokens per session scan B 352883b7abb7
setup is a skill published in the GitHub repository godshiba/genesis (2 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 1,848 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
vs-user-onboarding
Guide a brand-new SearchCLI/vs user from first-time usage questions to sign-up, purchase of Viking AI Search, AK/SK setup, and a working authenticated CLI. Use when the user says they downloaded or installed SearchCLI/vs and asks how to use it, how to start, sign up, buy, or onboard.
n8n-cli
Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.
zoom-meeting-scribe
Listen-only scribe workflow for Zoom meetings. Silently understand and record meeting transcripts delivered via RTMS, escalate only urgent matters to your supervisor, and post the report only after human approval once the meeting ends. Use when: receiving an inbox message with source=zoom (carrying a "[Zoom会議実況 チャンク#N…
sync-docs
Use when the user asks to sync, update, or refresh CLAUDE.md, AGENTS.md, SKILL.md, and README.md to reflect recent commits or PRs. Triggers on phrases like "sync docs", "update CLAUDE.md", "update AGENTS.md", "update SKILL.md", "update README", "reflect recent changes", or "document the recent PRs".
workflow-builder
Use when building and automating business workflows with Notion task tracking, Slack notifications, Kanban boards, and cross-functional process orchestration.
zapier-patterns
Use when zapier automation patterns — triggers, actions, filters, formatters, paths, code steps. Use when working with zapier patterns.