GENesis-AGI: Skill for Claude Code

.claude/skills/subsystem-map/SKILL.md

subsystem-map is a skill for Claude Code from WingedGuardian/GENesis-AGI. It costs 79 tokens per session (639 once invoked), scanned A, original, MIT.

A reference map of an AI system's major subsystems, their purposes, maturity, and boundaries. It is used as the starting point for checking what the system can or cannot do.

In plain words
What is it for?
It is for answering whether a capability exists, auditing the system, comparing it with another system, and reviewing or summarizing its architecture.
Why use it?
It prevents capability audits from relying on a cold search or an outdated assumption, especially when deciding whether something is missing.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is WingedGuardian/GENesis-AGI's own configuration. It tells Claude Code how to work on GENesis-AGI itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything GENesis-AGI configures →

Reuse

Borrowing it

Nothing to install: this file belongs to WingedGuardian/GENesis-AGI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/WingedGuardian/GENesis-AGI/main/.claude/skills/subsystem-map/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/WingedGuardian/GENesis-AGI

Made for: Claude Code.

Wrote 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.

agentmods badge for subsystem-map

README.md
[![agentmods](https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/subsystem-map.svg)](https://agentmods.dev/skills/wingedguardian/genesis-agi/subsystem-map)
Your own site
<a href="https://agentmods.dev/skills/wingedguardian/genesis-agi/subsystem-map"><img src="https://agentmods.dev/badge/skills/wingedguardian/genesis-agi/subsystem-map.svg" alt="Measured on agentmods" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 639 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.00639
Opus 5 $0.00039 $0.00319
Sonnet 5 $0.00016 $0.00128
Haiku 4.5 $0.00008 $0.00064

Measured 7d ago against content hash 1c1cacc8fcff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

subsystem-map 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 7d 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.

.claude/skills/subsystem-map/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The Rule

Read docs/architecture/CURRENT.md FIRST — before any grep, agent dispatch, or claim about what Genesis has or lacks. It is the canonical judgment-layer map: what each subsystem is FOR, its easy-to-forget mechanisms, maturity (live / shadow / dark), and do-not-touch edges.

A claim of absence ("Genesis lacks X", "Genesis should add X") made without consulting the map first is a protocol violation — the 2026-06-30 audit produced 6/7 wrong infrastructure claims exactly this way.

Workflow

  1. Locate the entry. Find the subsystem entry (or entries) covering the capability in question. Entries claim modules in fenced yaml subsystem-map blocks — the union covers every top-level package in src/genesis, so "no entry mentions it" means you're using the wrong concept name, not that it doesn't exist.
  2. Trust but verify. The map is judgment-layer, not ground truth. Check each entry's verified: <sha> <date> stamp; if its modules have moved since, re-verify the specific claim against the live tree before relying on it.
  3. Then enumerate. For absence/existence conclusions, follow the audit protocol (procedure codebase_audit / dev-skill "Auditing Existing Capabilities"): enumerate the subsystem's module inventory, trace the call graph both directions, grep by concept with synonyms, and verify against RUNTIME state (env gates, logs) — the map tells you where to look, not what to conclude.

Write-Back Duty

After you change a subsystem's capabilities (new mechanism, new gate, wiring flip, removal) or re-verify an entry during an audit:

  • Update the owning entry's prose and its modules: block if the package set changed.
  • Bump the entry's verified: stamp to the current short sha + date.

CI enforces the module partition (scripts/check_subsystem_map.py): a new top-level package that no entry claims fails the build; stale stamps warn.

Naming Trap

capability_map (DB table) and ego/capability_aggregator.py are the ego's per-domain self-confidence model — completely unrelated to this map. Never conflate them; everything here is "subsystem map".

Read the full file on GitHub · 59 lines

Changes

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.

  1. 7d ago First seen · 59 lines · 79 tokens per session scan A 1c1cacc8fcff

Subscribe to this mod's changes

subsystem-map is a skill published in the GitHub repository WingedGuardian/GENesis-AGI (95 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 639 once invoked, about $0.0004 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.