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-statusgit 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-status)<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-status"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-status/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-status"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-status.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.00028 | $0.00544 |
| Opus 5.5 | $0.00011 | $0.00218 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
Status 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
Status — Where Am I?
The pipeline dashboard. Reads on-disk state and reports. Never writes approval records — a deterministic filesystem read, no generative step. Runs any time.
Inputs (filesystem only)
.genesis/project-state.md(active feature, mode).genesis/features/<feature>/approvals/master.json(feature-level phases).genesis/features/<feature>/approvals/group-{N}.json(group progress)micro-specs/*.mdfrontmatter (per-spec status)units.json(lowfield unit progress)git status/git log(uncommitted work, recent commits)ghfor pending PRs (if available); aNEEDS_CLARIFICATIONmarker scan
Process
- Read
project-state.mdfor the active feature and mode. - Read
master.json; count micro specs per group from themicro-specs/directory. - If in implementation, read the active
group-{N}.jsonfor spec-level detail. - If lowfield, read
units.jsonfor unit progress. - Check for pending PRs and
NEEDS_CLARIFICATIONmarkers. - Render the dashboard (or JSON with
--json).--allshows every feature.
Output
FEATURE: <name> BRANCH: ... MODE: <mode> PHASE: ...
Pipeline:
[x] Brainstorm / Design / Specify / North Star / Micro Specs
[ ] Implement — G0: 4/4, G1: 2/6 <- current
[ ] Audits — G0: A1+ A2+ A3+ A4+ A5+, G1: pending
[ ] Final (F-pass)
Progress: 6/26 micro specs implemented PRs: 2 pending Blockers: none
Approval State: | Phase | Status | Disposition | Date | Notes |
Mode differences
Brownfield adds scope boundaries (files in/out of scope) and regression surface. Lowfield adds a unit-progress table with per-unit stage depth (e.g. 6/8 line-edit).
Natural language triggers
- "status"
- "where am I"
- "pipeline position"
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 · 54 lines · 28 tokens per session scan A dcd794a03f04
Status is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 544 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
backlog
Manage the project's tech debt backlog. Add, list, fix, wontfix, delete, prioritize, and suggest batch actions on tracked issues, run by the user to manage accumulated debt (skills file their findings through /.zuvo/backlog-add themselves, never through this skill). Modes: list [category], add [description], fix B- …
retro
Engineering retrospective from git metrics. Reports deployment frequency, release cycle span, churn hotspots, backlog health. Outputs narrative report with 3+ actionable items. Flags: --since, --path, explicit range argument.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
ccc-fable
Arm, check, audit or disarm the Commander Method: the PM loop, 12 checkable gates, workflow-first posture and verifier separation, persisted in Commander state. Use when the user says fable on/off/status/audit or wants verification-gated, orchestrated work.
ccc-linear
View your open Linear issues, pick one to work on (moves it to In Progress and creates a branch), create a new issue, or see a board overview, all from pickers. Use when the user types $ccc-linear, asks for their Linear issues or tickets, or wants to start work from a ticket.
ccc-onboard
Contributor first-hour plan for the current repository: reads CLAUDE.md, BIBLE.md and package.json, checks required tools, asks the contributor's role, and returns a five-step checklist plus five real starter resources. Use when someone new joins a repo or types $ccc-onboard.