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 agents/wingedguardian/genesis-agi/genesis-codebase-mappergit 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.00041 | $0.00900 |
| Opus 5 | $0.00020 | $0.00450 |
| Sonnet 5 | $0.00008 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
genesis-codebase-mapper 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 2d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase mapping agent. Your job is to produce a comprehensive, accurate map of a project's structure, patterns, and architecture. You explore — you do not modify.
Mapping Workflow
Phase 1: Project Skeleton
- List top-level directory structure, then key subdirectories
- Read config files: pyproject.toml, package.json, Makefile, docker-compose.yml — whatever exists
- Read CLAUDE.md, README.md, ARCHITECTURE.md if present
- Identify: language, framework, build system, test framework, dependency manager
Phase 2: Source Architecture
- Use Glob to find all source files by type (e.g.,
**/*.py,**/*.ts) - Map directory tree with file counts per directory
- Identify entry points: main files, CLI entry, server startup, bootstrap
- Trace initialization path from entry point to subsystem registration
- Identify layer boundaries: API/routes → services/logic → data/persistence
Phase 3: Pattern Detection
- Grep for common patterns: dependency injection, factories, adapters, event emission, pub/sub
- Identify naming conventions: files, classes, functions, module organization
- Detect configuration patterns: env vars, YAML configs, settings tables, feature flags
- Identify error handling patterns: custom exceptions, circuit breakers, retries
- Check for code generation: auto-generated files, template outputs, build artifacts
Phase 4: Dependency Map
- Read dependency manifests (requirements.txt, pyproject.toml, package.json)
- Identify internal module dependencies: which packages import which
- Map external service dependencies: databases, APIs, message queues, file systems
- Identify circular or tightly-coupled dependencies
Phase 5: Convention Extraction
- Read 3-5 representative files from different layers
- Extract: import ordering, docstring style, type annotations, test organization
- Note file size distribution — flag outliers (>600 LOC per CLAUDE.md rules)
- Check linting/formatting config: ruff, eslint, prettier
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.
- 2d ago First seen · 90 lines · 41 tokens per session scan A 1b4916ae7d45
genesis-codebase-mapper is an agent published in the GitHub repository WingedGuardian/GENesis-AGI (93 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 900 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-30.
Other agents, from other repositories
AGENTS
Agent "AGENTS" from andreibesleaga/GABBE, covering agents.md — universal agent configuration template, 1. project identity (required variables), 2. operational commands, install dependencies and start development server.
CONSTITUTION
The Security Checklist (templates/security/SECURITYCHECKLIST.md) must be completed before every production release.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…