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/issuenpx skills add godshiba/genesis --skill issuegit 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/skills/godshiba/genesis/issue)<a href="https://agentmods.dev/skills/godshiba/genesis/issue"><img src="https://agentmods.dev/badge/skills/godshiba/genesis/issue.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.00563 |
| Opus 5 | $0.00039 | $0.00282 |
| Sonnet 5 | $0.00016 | $0.00113 |
| Haiku 4.5 | $0.00008 | $0.00056 |
Grade A, and why
issue 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 3d 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
/genesis:issue — Register an Issue
Append one entry to the Open section of docs/registry/ISSUES.md. A problem
in a TODO comment is invisible; a problem with an ISS number is work.
Steps
- Determine the next sequential ID by scanning existing
ISS-entries (including Resolved). - Pick severity:
high(blocks or corrupts),medium(wrong but survivable),deferred(intentional, revisit later). If unclear from context, default tomediumand say so. - Write the entry in the file's format: title, severity, registered date (today's real date), context with file paths, and a concrete investigation path — the first commands or files whoever picks this up should look at.
- GitHub mirror — only when every condition holds, else skip silently.
Mirror to GitHub only if all of these are true:
GENESIS_GITHUBison(defaultoff— GENESIS never touches GitHub unless opted in via/genesis:config); agithub.comremote exists;ghis installed (command -v gh); andgh auth statussucceeds. When all hold, rungh issue create --title "ISS-NNN: <title>"with a body pointing at the canonical ISSUES.md entry, then back-fill the**GitHub:** [#N](url)line. If any condition is missing, the issue stays local — skip without a word, never a blocker, never a prompt.ghis a separate CLI that acts on GitHub's servers; treat it as opt-in, capability-checked, and side-effecting. - If the code contains a related TODO/FIXME, rewrite it to cite the ID:
// TODO(ISS-NNN): .... - Confirm in one line:
ISS-NNN registered (severity) — <title>.
Resolving (when asked): move the entry under Resolved with a dated note — never delete — and, if GitHub mirroring is enabled and a mirror exists, close it in the same commit.
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.
- 3d ago First seen · 38 lines · 79 tokens per session scan A 2d32a93fbde4
issue is a skill published in the GitHub repository godshiba/genesis (2 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 563 once invoked, about $0.0004 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 skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
verify-security
安全校验关卡。自动扫描代码安全漏洞，检测危险模式，确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变更、攻防任务、重构完成时自动触发。.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:human-like-code-review
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.