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-implementgit 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-implement)<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-implement"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-implement/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-implement"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-implement.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.00040 | $0.00643 |
| Opus 5 | $0.00020 | $0.00321 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
Implement 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 10d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement — One Spec, One Commit, One PR
Implement exactly one micro spec per invocation. The micro spec is the complete instruction set — no task selection, no group management. Write the code/content for the files in its File Operations table, verify against its acceptance criteria, then commit.
Gate: the active group's micro specs are written and the prior phase is accepted. Followed by the A1–A5 audits once the group's specs are all implemented.
Inputs
- The single target micro spec at
.genesis/features/<feature>/micro-specs/{spec-id}.md(the complete instruction set). .genesis/project-state.md(mode), the constitution,northstar.md.approvals/master.json/approvals/group-<N>.jsonfor position.- The files listed in the spec's
readsinterface.
Process
- Pre-flight: confirm the feature/group/spec and that the prior phase is accepted; read the target spec in full.
- Implement (mode-branched):
- Greenfield: implement the files in the File Operations table; satisfy every FR/AC; write tests per the constitution.
- Brownfield: stay strictly within the spec's File Operations table (scope discipline); preserve existing behavior; classify any touched code inherited vs introduced via git blame; ensure no regressions.
- Lowfield: produce the stage's artifacts per the declared artifact schema; verify the schema validates.
- Verify: run the project's
build/test/lintcommands as declared in the constitution, and confirm the spec's acceptance criteria pass. Do not write outside the spec's File Operations table. - Finalize: one commit scoped to the spec (
implement: {spec-id} — {title}), then open one PR. Log any failed approaches totried.jsonso they are not retried.
Anti-laziness
What you write runs. No stubs, no TODO, no "simplified version," no narrowing the spec to dodge it. A change is not done at the first file — sweep the blast radius named in the File Operations table (callers, types, tests, configs). If the spec cannot be satisfied as written, stop and surface why — do not ship a partial.
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.
- 10d ago First seen · 51 lines · 40 tokens per session scan A 30792b4c32f1
Implement is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 643 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
pr-package
Prepare a clean delivery package for GitHub from the real git diff vs an explicit base branch, persisted as PRPACKAGE.md (or PRPACKAGE. .md for multi-repo tasks). Produces branch name, commit messages, fetch, checkout, add, commit, and push commands, PR title and body, and reviewer attention points; never invents work…
branch-commit
Return a branch name and a concise commit message (at most 2 lines) for the current task, grounded in the real git diff rather than a paraphrase of the task summary, and with --apply optionally create that commit after showing it and getting the user's confirmation in the same turn. Use when the user only needs quick…
task-workspace
Provision, report, or attach a dedicated git worktree and branch for the active task on a git-backed project, so multiple tasks run in parallel on one repository without colliding on a single working tree. Opt-in and git-gated: a non-git project or an un-opted task is a no-op. Records the worktree path and task branch…
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
polyphony
Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…