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-northstargit 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-northstar)<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-northstar"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-northstar/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-northstar"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-northstar.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.00033 | $0.00658 |
| Opus 5 | $0.00016 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
North Star 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
North Star — The Perfect World
Write the North Star: a first-person, no-compromise vision of the feature in a perfect world, plus weighted Quality Dimensions and The Compass (decision filters for subjective choices). It is the qualitative reference every later audit — especially A4 and the F-pass — measures against.
Gate: the specify phase must be accepted. Requires the spec and design docs.
Inputs
.genesis/project-state.md(mode).genesis/features/<feature>/spec.md(required),design.md(required),brainstorm-log.md- The constitution
approvals/master.json(verify specify accepted)
Process
- Resolve the feature name; handle an existing North Star (revise in place, or archive to
northstar-v{N}.mdand write fresh) and partial-file resumption. - Deep-read the entire master spec — every FR, AC, user story, NFR.
- Write
northstar.mdfromnorth-star-template.md, in first person, four sections:- The Perfect World — narrative of the feature when every requirement is perfectly met; experience, not mechanism; mode-aware.
- Quality Dimensions — feature-specific dimensions, each weighted Critical / Important / Nice, each with what it means, a concrete and testable "what perfect looks like," and one test question. Always include Zero-Tolerance Quality (Critical).
- The Emotional Quality — "for the user" and "for the builder," mode-aware.
- The Compass — decision filters phrased as questions, mode-aware.
- No-compromise validator (up to 3 iterations): strip implementation detail, timeline language ("in v1", "for now", "later"), compromise language ("MVP", "good enough", "adequate"), and vague quality terms; fill missing perspectives; rewrite product-brochure voice into a grounded one. Concrete is allowed ("sub-100ms"); naming implementation is not ("Redis cache").
- Constitution-compliance check; present; commit.
Mode differences
- Greenfield: the perfect technical system.
- Brownfield: perfect integration (no regression, clean boundaries); add the compass question "Does this respect what exists?"
- Lowfield: perfect content pipeline (every stage and artifact earns its place); add "Does this serve the domain or just the process?"
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 · 53 lines · 33 tokens per session scan A d62bc460e9af
North Star is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 658 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".