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/allgpt-co/quickvoice/codebase-mappernpx skills add allgpt-co/QuickVoice --skill codebase-mappergit clone --depth 1 https://github.com/allgpt-co/QuickVoiceWhat 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.00028 | $0.03755 |
| Opus 5 | $0.00014 | $0.01878 |
| Sonnet 5 | $0.00006 | $0.00751 |
| Haiku 4.5 | $0.00003 | $0.00376 |
Grade A, and why
gsd-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 yesterday.
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 — 728 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Codebase Mapper
Explores a codebase for a specific focus area and writes analysis documents directly to .planning/codebase/.
When to Use
Use this agent when:
- You need to understand an existing codebase structure
- Starting work on a brownfield project (existing code)
- Need to document technology stack, architecture, or patterns
- Want to identify technical debt and concerns
- Preparing for a new phase that requires codebase context
Focus Areas
The mapper is spawned with one of four focus areas:
- tech - Analyze technology stack and external integrations → writes STACK.md and INTEGRATIONS.md
- arch - Analyze architecture and file structure → writes ARCHITECTURE.md and STRUCTURE.md
- quality - Analyze coding conventions and testing patterns → writes CONVENTIONS.md and TESTING.md
- concerns - Identify technical debt and issues → writes CONCERNS.md
Core Responsibilities
- Explore thoroughly - Read relevant files, understand patterns, identify key components
- Write directly - Create documents in
.planning/codebase/to reduce orchestrator context load - Be prescriptive - Document HOW things are done, not just WHAT exists
- Include file paths - Every finding should have a file path in backticks for navigation
- Return confirmation only - Don't return document contents, just confirm what was written
Why This Matters
These documents are consumed by other GSD commands:
/gsd:plan-phase loads relevant codebase docs when creating implementation plans:
| Phase Type | Documents Loaded |
|---|---|
| UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
| API, backend, endpoints | ARCHITECTURE.md, CONVENTIONS.md |
| database, schema, models | ARCHITECTURE.md, STACK.md |
| testing, tests | TESTING.md, CONVENTIONS.md |
| integration, external API | INTEGRATIONS.md, STACK.md |
| refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
| setup, config | STACK.md, STRUCTURE.md |
/gsd:execute-phase references codebase docs to:
- Follow existing conventions when writing code
- Know where to place new files (STRUCTURE.md)
- Match testing patterns (TESTING.md)
- Avoid introducing more technical debt (CONCERNS.md)
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.
- yesterday First seen · 728 lines · 28 tokens per session scan A ace0e09769f8
gsd-codebase-mapper is a skill published in the GitHub repository allgpt-co/QuickVoice (492 stars, last pushed 20d ago), licensed MIT. It adds 28 tokens to every session and 3,755 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
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.
gsd-codebase-mapper
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area.
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
docingest-docs
Find, search, and read approved documentation snapshots through DocIngest.
knowledge-absorber
深度解析链接/文档/代码，生成导师级教学笔记 + Wan 2.7 知识海报。 Use when user asks to: 学习、分析、解读、整理、吸收、读懂 任何文档或代码 Trigger keywords: 学习、分析、知识卡片、知识海报、解读文档、整理笔记、知识库、存入知识库 支持 PDF/Word/Markdown/代码/图片，自动真理锚定验证，国学内容自动水墨风格。 When user provides: URL链接、文件路径、代码文件、图片 → 生成知识卡片 When user says: "生成海报"、"知识海报" → 额外生成 Wan 2.7 信息图.
livekit-simulations
Generate targeted test scenarios for a LiveKit voice or chat agent and run them as simulations — locally, from the agent's own code plus what the user wants stress-tested. Use whenever the user wants to "test my agent", "what should I test", "create/generate simulation scenarios", "make a sim test suite", "use lk…