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 gate-checkgit 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/gate-check)<a href="https://agentmods.dev/skills/godshiba/genesis/gate-check"><img src="https://agentmods.dev/badge/skills/godshiba/genesis/gate-check.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.1 | $0.00078 | $0.00691 |
| Opus 5 | $0.00039 | $0.00345 |
| Sonnet 5 | $0.00016 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
gate-check 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/genesis:gate-check — Audit the Seven Gates
Audits the working tree against every gate and reports pass/fail per gate. This skill never fixes silently — it reports, then offers to fix.
Requires a GENESIS project (docs/registry/ exists). If absent, say so and
suggest /genesis:init.
If this is not a git work tree, skip the git-based parts (the untracked/new-file scan for G1, the diff-vs-default-branch for G4) and audit what changed this session against the registries instead — never report a git fact that does not exist.
For large diffs (10+ changed files), delegate the audit to this plugin's
gate-auditor agent (registered as genesis:gate-auditor) via the Agent tool
and relay its report. Otherwise run inline:
The checks
G1 Registration — git status --porcelain for untracked/new files (and
new files in the diff against the default branch). Each must appear in
docs/registry/FILES.md. List missing ones.
G2 Validation — find the check command in CLAUDE.md (the command marked as the validation gate) and run it. Red output means G2 FAIL and the overall result is FAIL regardless of other gates. Never report overall pass on a red check command. Quote the failing output.
G3 Issue — grep changed files for TODO, FIXME, HACK, XXX markers
that do not reference an ISS- ID. Each is a G3 violation: it belongs in
docs/registry/ISSUES.md.
G4 Doc-sync — read the Doc-Sync Map table in CLAUDE.md. For each changed area, check whether the mapped doc was also modified (in the diff or working tree). Flag stale pairs.
G5 Landmine — judgment check, not mechanical: did this session hit
surprising behavior, a debugging detour, or an environment quirk? If yes and
docs/registry/LANDMINES.md was not touched, flag it and draft the entry.
G6 Decision — judgment check: did this work choose between real alternatives (library, pattern, schema)? If yes and DECISIONS.md was not touched, flag it and draft the entry.
G7 Session — informational here (the Stop hook and /genesis:close
enforce it): note whether SESSION_LOG.md has an entry covering this work.
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.
- 7d ago First seen · 59 lines · 78 tokens per session scan A 57e4f33385db
gate-check is a skill published in the GitHub repository godshiba/genesis (2 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 691 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
tenacity
Drive the work to actually-done — fresh verification of every claim, context-isolated diff review, cleanup, commit, post-mortem. Use when a tracked piece of work is ready to close out, whether it moved through slices or was built directly after Wonder without them.
dw-next
Continue the change you are in the middle of, from where the last session had to leave it: catch up on where it stands and what is left, then build every unticked task, one commit each. Its state is read back from the doc, never from the conversation, so it survives a /clear.
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
cleanup
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it. Use when asked to work a ticket end-to-end.
merge
Merge the reviewed pull request for the current branch, then hand straight off to cleanup. Use when a human green-lights an open PR.