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/integrate-modulenpx skills add WingedGuardian/GENesis-AGI --skill integrate-modulegit clone --depth 1 https://github.com/WingedGuardian/GENesis-AGIWrote 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/wingedguardian/genesis-agi/integrate-module)<a href="https://agentmods.dev/skills/wingedguardian/genesis-agi/integrate-module"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/integrate-module.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.01622 |
| Opus 5 | $0.00013 | $0.00811 |
| Sonnet 5 | $0.00005 | $0.00324 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
integrate-module 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Module
Turn any external program into a Genesis module. This is the standardized process for plugging a program into Genesis — whether it was built for Genesis or not.
Genesis is the nervous system. The program is the body. This skill builds the connection between them.
When to Use
- User says "integrate X into Genesis" or "make X a module"
- User wants to plug an external program, service, or tool into Genesis
- User wants Genesis to drive, monitor, or interact with an external system
- Ego session discovers a program worth integrating and proposes it
Input
One of:
- Running service URL (e.g.,
http://your-host:8080) - Repository URL (e.g.,
github.com/user/repo) - Local path (e.g.,
~/my-tool/) - Description (e.g., "a job automation tool running on my server")
Phase 1: Discovery
Goal: Understand what the program does, how it communicates, and what Genesis can connect to.
If running service:
- Probe for health endpoints:
/health,/api/health,/status,/ - Probe for API documentation:
/docs,/openapi.json,/swagger.json - If OpenAPI spec found: parse all endpoints, methods, parameters
- If no spec: probe common REST patterns, check response shapes
- Record: base URL, available endpoints, response formats, auth requirements
If repository:
- Clone or read the source
- Identify tech stack (language, framework, database, scheduler)
- Find entry points: route definitions, CLI commands, main functions
- Map API endpoints from source (FastAPI routes, Express handlers, etc.)
- Identify configuration: env vars, config files, secrets needed
- Check deployment method: Docker, systemd, kubernetes, manual
- Record: full capability map from source
If description only:
- Ask the user for more details: where does it run? how do you access it?
- Attempt to locate the service or source based on what they share
- Fall back to manual endpoint mapping with user guidance
Output of Phase 1:
A structured assessment:
Program: [name]
Location: [URL / path / host]
Tech Stack: [language, framework, DB]
Communication: [HTTP API / CLI / stdin / socket]
Endpoints Found: [count]
Auth Required: [yes/no, method]
Health Check: [endpoint, expected response]
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.
- 5d ago First seen · 187 lines · 25 tokens per session scan A c433472b3bdb
integrate-module is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (93 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,622 once invoked, about $0.0001 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-30.
Other skills, from other repositories
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).
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…
figure
Hybrid figure pipeline (Nano Banana raster + rembg background removal + TikZ vector assembly). Includes a TikZ template library covering quantum circuits (quantikz), Feynman diagrams (tikz-feynman), circuits (circuitikz), molecules (chemfig), 2D/3D plots (pgfplots), energy-level diagrams, phase-space trajectories…
memory
Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.
compute-methods
Environment-verified friction sheets for field-standard computational tools (Rydberg pair interactions, QEC circuits, qLDPC decoding, code distance, atom dynamics, optics, quantum chemistry). Each sheet lists the tools the field actually uses, the first-use frictions that make agents wrongly abandon them, and one-line…
context-window-management
Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot.