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 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/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/skills/godshiba/genesis/issue"><img src="https://agentmods.dev/badge/skills/godshiba/genesis/issue.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.00079 | $0.00563 |
| Opus 5.5 | $0.00032 | $0.00225 |
| Sonnet 5.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 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
/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.
- 1mo 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 4mo ago), licensed MIT. It adds 79 tokens to every session and 563 once invoked, about $0.0003 per session on Opus 5.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
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
gza-task-triage
Triage gza incomplete rows — classify each unresolved merge-unit lineage and recommend the right corrective action (drop moot leaves, escalate to fix, surface manual-resolve rebases, etc.). Never merges, retries, resumes, or deletes branches; never edits code.
bug-capture
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug"…
defect
A command for registering a software defect, meaning behavior that does not work as intended, and creating a task to fix it. The defect and its fix task receive tracked IDs and are stored in the project's backlog and task folders.
setup-working-genius
Per-repo configuration — pin the work-file directory, verify commands, and issue tracking, seed the project docs, and leave the pointer that tells every future session this project works this way.