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-specifygit 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-specify)<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-specify"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-specify/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-specify"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-specify.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.00038 | $0.00986 |
| Opus 5 | $0.00019 | $0.00493 |
| Sonnet 5 | $0.00008 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
Specify 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 11d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specify — The WHAT
Produce the master spec: user stories, functional requirements (FRs), non-functional requirements (NFRs), acceptance criteria (ACs), and the micro-spec plan that breaks the feature into dependency-ordered groups of small implementation units. Strictly WHAT — never HOW.
Gate: the feature's design phase must be accepted (else "Accept the design first").
Inputs
.genesis/project-state.md(mode)- The constitution
.genesis/features/<feature>/design.md(required).genesis/features/<feature>/brainstorm-log.md(optional).genesis/design/overview.mdand other relevant design docsapprovals/master.json(verify design accepted)
Process
- Resolve the feature name; handle an existing/partial spec (revise vs continue vs fresh).
- Write
spec.mdfromspec-template.mdwith all 14 sections:- Overview · 2. Design Document References · 3. User Stories · 4. Functional Requirements (
FR-001…, RFC-2119 MUST/SHOULD/MAY) · 5. Non-Functional Requirements (NFR-001…) · 6. Acceptance Criteria (AC-001…, EARS form "WHEN {trigger}, THE SYSTEM SHALL {behavior}", each linked to an FR) · 7. Agent Boundaries (Always / Ask First / Never) · 8. Changelog Preview · 9. Out of Scope · 10. Assumptions (A-001…) · 11. Open Questions · 12. Constitution Compliance Check · 13. Micro Spec Plan · 14. Changelog.
- Overview · 2. Design Document References · 3. User Stories · 4. Functional Requirements (
- Section 13 — the Micro Spec Plan: groups ordered by dependency. For each group list its micro specs (ID, title, description, dependencies, size S/M/L/XL); include totals (group count, spec count, critical path). Two safeguards:
- Shared Infrastructure column — any file touched by 2+ specs gets exactly one owner group responsible for auditing it.
- Cross-Cutting FRs table — FRs spanning 2+ subsystems (keywords across/between/coordination/handoff) are each assigned to one micro spec at the integration point, so they don't fall through audit cracks.
- Zero implementation detail — no file paths, function names, endpoints, or schemas. Deferred items go to Out of Scope with a note on which spec they belong in.
- If the spec depends on other features, write
dependencies.json(shape below); skip the file if none. - Self-validation pass (up to 3 iterations): catch implementation leaks, vague requirements, missing strength keywords, FRs without ACs, untestable ACs, incomplete user stories, mode mismatch; auto-correct and report.
- Constitution-compliance check; insert
<!-- NEEDS_CLARIFICATION: {question} -->markers for residual ambiguity; recommend/genesis-clarifyif any remain. Present; commit; updateproject-state.md.
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.
- 11d ago First seen · 67 lines · 38 tokens per session scan A f9810f40a3c6
Specify is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 986 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".
implementation-plan
Define an incremental, reviewable, production-safe implementation plan for the active task and persist it as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update. Breaks work into the smallest safe slices with objective, exact scope, ordering rationale, key risks, validation approach, exit criteria, and work complexity…