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 Nagiliant/Genesis-Legacy-V2 --skill genesis-clarifygit clone --depth 1 https://github.com/Nagiliant/Genesis-Legacy-V2Wrote 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/nagiliant/genesis-legacy-v2/genesis-clarify)<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-clarify"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-clarify/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/nagiliant/genesis-legacy-v2/genesis-clarify"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-clarify.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.00036 | $0.00648 |
| Opus 5 | $0.00018 | $0.00324 |
| Sonnet 5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
Clarify 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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarify — Close the Holes
A post-spec review that finds and closes gaps before the North Star. Gate: the specify phase must be accepted (else "Accept the spec first").
Inputs
.genesis/project-state.md(mode).genesis/features/<feature>/spec.md(required),design.md(required)brainstorm-log.md(optional), the constitutionapprovals/master.json(verify specify accepted)dependencies.jsonfor this feature and its peers (cross-feature coverage check)
Process
- Resolve markers. Scan the spec for
NEEDS_CLARIFICATIONmarkers; resolve each one at a time (question → impact → suggested answer), updating the spec and removing the marker. (--markers-onlystops here.) - Coverage scan across 11 categories, rating each Clear / Partial / Missing: Functional Scope · Domain/Data Model · Interaction/UX · Non-Functional Quality · Integration/Dependencies · Edge Cases · Constraints/Tradeoffs · Terminology · Completion Signals · Assumptions · Cross-Feature Dependencies. (
--scan-onlyreports and stops.) - Ask at most 5 targeted questions per run, prioritized by impact, focused on Partial/Missing categories, each with a recommended answer.
- Apply answers one at a time — update the spec immediately after each (refine requirements, add edge cases to FRs, document assumptions, strengthen/add ACs, remove resolved open questions).
- (
--simulate) Run 5–10 usage scenarios against the spec text — for each, trace FRs/ACs and mark PASS (spec handles it) or GAP (it doesn't). Gaps become new questions or amendments. - Re-run constitution compliance if scope changed (halt on violations).
- Present a before/after coverage summary table (+ simulation table if used). Commit; update
project-state.md.
Mode differences
Each category is mode-aware: greenfield checks completeness of new capability; brownfield checks new-vs-modified classification, preservation of existing behavior, and scope-boundary explicitness; lowfield checks pipeline-stage and artifact-schema completeness and measurable per-stage gates. Simulation likewise differs — greenfield = standard usage; brownfield = migration paths and backward compatibility; lowfield = pipeline at scale (50+ units), mid-stream entry, stage skipping.
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.
- 12d ago First seen · 48 lines · 36 tokens per session scan A 827cad06879a
Clarify is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 648 once invoked, about $0.0002 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
auth-doctor
Diagnose and fix issues in existing auth setups. Scans environment, files, security, middleware, OAuth, database, and dangerous code patterns. Produces scored health report with actionable fixes.
init
Set up the Claude Code harness for this project. Configures CLAUDE.md, permissions, hooks, MCP servers, agents, and SSOT docs based on your stack and chosen tier. Run on first setup or when CLAUDE.md is missing or has [PLACEHOLDER] markers. Trigger phrases: "set up harness", "configure claude", "onboard project"…
new-project
Start a new project from scratch. 3-phase interview: project goals → tech stack → architecture → conventions. Scaffolds using official tools then configures the Claude Code harness. Run on an empty directory. Trigger phrases: "start a new project", "create project from scratch", "greenfield setup", "I have an empty…
setup-memory
Configure project memory: write CLAUDE.md with architecture context and (Tier 3) set up a self-sustaining .claude/memory/ lifecycle — SessionStart load hook, Stop save-nudge hook, and a /save-memory skill that distills each session. Called by init or standalone to configure the memory pillar. Trigger phrases: "setup…
optimize-harness
Analyze Claude Code tool call logs and suggest harness improvements based on actual usage patterns. Requires observability enabled + 7 days of data. Trigger phrases: "optimize harness", "harness suggestions", "improve my setup", "analyze tool usage", "what hooks should I add".
setup-skills
Install reusable project skills into .claude/skills/. Ships git-workflow (commit/branch/PR conventions from your init choices). Triggers: "setup skills", "install project skills", "add git skill".