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 agentmods add skills/wingedguardian/genesis-agi/genesis-developmentnpx skills add WingedGuardian/GENesis-AGI --skill genesis-developmentgit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWhat 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 | $0.00115 | $0.27361 |
| Opus 5 | $0.00057 | $0.13681 |
| Sonnet 5 | $0.00023 | $0.05472 |
| Haiku 4.5 | $0.00012 | $0.02736 |
Grade A, and why
genesis-development scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
endpoint** (`curl` the real server) or running inside the real service — not How it starts
The opening of the file, as written. The whole thing — 1,730 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Gate
Before reading any reference, confirm the task is Genesis-development, not Genesis-as-tool. If uncertain, ask the user: "Are we modifying Genesis itself, or using Genesis for something else?"
On-Load Mindset
Internalize these immediately when this skill fires — they shape how to work from the start, not just what to check before commit.
Wiring Discipline
Every new component needs at least one call site in the actual runtime path. Apply this 4-level verification taxonomy:
- Exists — file/function present. Proves nothing.
- Substantive — tests pass, handles happy + error. No runtime proof.
- Wired — live call site, import chain unbroken. Minimum for "done."
- Data-Flow Verified — real data flows end-to-end. Required for critical paths.
Mark nothing "done" below Level 3.
GROUNDWORK Code Is NOT Dead Code
Code tagged # GROUNDWORK(feature-id): why is intentional future
investment. Never delete or refactor it as dead code. Only remove when
the feature is fully active or the user explicitly cancels it.
Architecture Review
For medium-to-large Genesis work (3+ files, new components, wiring
changes), dispatch a genesis-architect subagent before implementation
to check dependencies, edge cases, and DRY violations. Small targeted
changes skip this.
Timeout Policy
The burden of proof is on you to justify why a timeout should exist. Do not default to "add a timeout for safety." Instead:
- Identify the specific failure mode. What hangs? Why? Is there evidence this actually happens, or is it speculative?
- Justify the specific value. Why this number and not another? What legitimate work would be killed at a lower value?
- If you have no strong justification for a specific value, default to 2 hours (7200s). This is the project floor — generous enough to never interfere with legitimate work while preventing permanent resource lockout from truly hung processes.
- Surface the request to the user with the value, the failure mode, and the evidence. Never add a timeout as a "small improvement" or "defense in depth."
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +158 lines 05e86ed774b7
- yesterday First seen · 1,572 lines · 115 tokens per session scan A c3c76fc46ecb
genesis-development is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (93 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 27,361 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
survey-methodology
Plan-time methodology contract for survey/review/report projects. Forces an audit-grade survey instead of a paper-trust summary. Distilled from 240 reviews (2024-2026) across 9 domain clusters — physics/RMP/Living Reviews, chemistry/materials, biology/medicine narrative + Cochrane SRs, CS/ML/AI, math/Acta Numerica…
review
Write domain-authentic review articles that synthesize rather than stack. Covers 10 scientific domains (physics, chemistry, biology, medicine, mathematics, computerscience, earthenvironment, astronomy, economics, materials) with per-domain style guides mined from landmark reviews in RMP / Nat. Rev. X / Annu. Rev. /…
search
Unified academic paper search, citation chains, paper download (arXiv LaTeX/PDF, Sci-Hub), figure extraction from papers, LaTeX source reading, BibTeX fetching, web search, and browser automation for Cloudflare-protected sites (PRL, Science, Nature, Google Scholar).
matplotlib-figures
Publication-quality data plots via matplotlib with venue-specific styles. Use for generating your own figures (timelines, comparison charts, data summaries, heatmaps) that you add to the LaTeX report. Your brain prompt supplies the venue-specific style directory as {{VENUESPECIFICDIR}} — use that value wherever this…
qec-construct
Verifier-in-the-loop CONSTRUCTION of quantum error-correcting codes with transversal non-Clifford gates (CCZ/T). Applies whenever the project goal is a new or better code/construction — INCLUDING search-phrased goals ("find codes beating X"), where the construct-loop (propose algebraic rule → qverify → debug) is the…
venue-specific
Venue-specific formatting requirements for academic journals and conferences across all disciplines. Covers Nature, Science, Cell, PRL, NEJM, Lancet, JACS, NeurIPS, ICML, and 30+ top venues. Use when writing, formatting, or checking a paper for a specific target venue.