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-microgit 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-micro)<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-micro"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-micro/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-micro"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-micro.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.00026 | $0.00876 |
| Opus 5.5 | $0.00010 | $0.00350 |
| Sonnet 5.5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
Micro 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Micro — Write One Group's Specs
Write all micro specs for one group in a single invocation. Each micro spec is a fully self-contained implementation unit — readable without the master spec — carrying its own objective, the full text of the FRs/ACs it covers, a File Operations table, acceptance criteria, and implementation notes.
Gate: the northstar phase must be accepted, AND the group must have a brainstorm entry (/genesis-brainstorm --boundary micro for G{N}).
Inputs
.genesis/project-state.md(mode)spec.md(required — for the Section 13 plan),northstar.md(required),design.md,brainstorm-log.mdapprovals/master.json(verify northstar accepted)- The constitution; any existing specs in
micro-specs/
Process
- Parse the group number
G{N}(refuse if missing). - Read Section 13; extract the group's specs (IDs, titles, dependencies, sizes). Cycle-detect the within-group dependency graph; refuse on a cycle. Verify the group exists in the plan.
- Create
.genesis/features/<feature>/micro-specs/. - Write specs sequentially in topological dependency order — write one, validate, save, commit, then the next. No batching, no parallel authoring. For each spec, from
micro-spec-template.md:- Frontmatter: title, spec-id, group, feature, status, dependencies, covers (FR/AC), deferred, reads, writes.
- Objective; Requirements Covered (full FR/AC text, not just IDs); Dependencies table; content sections; Acceptance Criteria; File Operations (create/modify/delete, mode-aware); Implementation Notes; commit message + PR description.
- Self-contained check: an implementer must be able to build from this spec alone — all FRs/ACs in full text, paths specific, ACs objectively verifiable.
- Size check: >500 lines → warn and auto-split into
{G.S.1}/{G.S.2}if reasonable (update the plan); else note and proceed. - Validate the frontmatter schema, stamp
last_validated, then commit.
- Coverage verification: every FR and AC assigned to the group is covered by at least one spec; report any uncovered.
- Produce group simulation scenarios (mandatory) covering functional flows, UI/UX states, integration points, stress scenarios, regression risks.
- Produce a human testing checklist for hands-on testing after merge.
- Final commit for plan updates + simulations + checklist.
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 · 60 lines · 26 tokens per session scan A 93db94070171
Micro is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 876 once invoked, about $0.0001 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
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
test-runner
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
test-first
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.
bidirectional-differential
Audit coherence across an arrow of intent by running two parallel fresh Claude sessions — one reconstructs code from a single EARS, the other reconstructs the EARS from stripped code — then classifies the drift between them. Use when the user invokes /differential-audit, asks to audit EARS-to-code drift for a feature…