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 skills add BuildrAI/Buildr --skill code-mapgit clone --depth 1 https://github.com/BuildrAI/BuildrWrote 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/buildrai/buildr/code-map)<a href="https://agentmods.dev/skills/buildrai/buildr/code-map"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/code-map/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/buildrai/buildr/code-map"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/code-map.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.01008 |
| Opus 5.5 | $0.00013 | $0.00403 |
| Sonnet 5.5 | $0.00007 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
code-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 1mo 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.
What it actually says
代码地图（Code Map）
把已确认的代码架构与实际实现组织表达为可阅读、可追溯的地图。代码结构由 code-architecture 指导，本技能（Skill）解释当前实现；采用架构要求时先核对差异，不通过改地图掩盖不符合要求的代码。
包含什么
地图是在用户理解与真实事实源之间提供的解释性导航。按主题纳入相关规范、前后端实现及必要配置，说明“规范要求什么、实现怎样组织、两者怎样对应”；独立的成果文件树列出文章、地图、图源、展示与依据，区分事实源和解释成果。范围以阅读问题为准，不收录无关文件，也不把单纯资料目录当地图。
每个被阅读文件提供经核实的总体说明，解释职责、关键协作及边界；由网页先展示说明再显示源文件。源码变化后核对说明，缺少依据时如实标明。具体原生文件树格式及可选阅读字段见网页阅读关联。
制作与维护
- 确定项目（Project）、服务（Service）、业务模块或流程范围及阅读问题。读取相关规范、架构约束、实际代码与调用方，明确哪些内容不在本图范围内。
- 按职责分区，先说明相关规范约束、实现职责和协作，再列带说明的可点击目录与文件。明确路径相对于哪个项目或服务根，只展示定位所需祖先及相关分支；使用原生 Markdown 嵌套列表与文件链接，加粗作者确认的业务目录，作为默认展开边界；祖先可见、业务目录内部默认收起，具体文件由用户继续展开。不把纯文本树和同内容宽表重复呈现。前后端沿用各自语言和框架；业务模块、接口、应用、数据访问、领域对象及共享能力只有实际存在才呈现。目录树是定位方式，不代替职责解释；相关资料清单也不是地图。
- 解释实际存在的接口入口（HTTP、CLI 等）、应用用例、领域规则、数据访问和基础技术支撑怎样协作；没有某层或采用文件存储时如实说明。依据
code-architecture判断职责，不为对齐模板补造目录或数据库。解释必要的依赖方向、数据归属和副作用。技能（Skill）以“中文用途（标识）＋职责”表格表达，链接进入详情；源文件名不是主标签。技能（Skill）工作方法与运行代码分开，工作协作不冒充函数调用。独立下探止于文件；方法可在文件说明中出现，不要求建设逐行索引。 - 文件移动时更新位置；职责变化时核对解释与协作；删除时先查替代实现再解除失效引用。保留未受影响内容，当前实现、建议结构与未核实信息明确区分。
- 核对每个已声明路径、职责与关键关联。记录来源观察、实际验证及未覆盖范围；目录存在不能证明语义正确。启用网页知识阅读时同时维护局部
knowledge/index.yml的对象、成果与来源，不复制正文；具体格式与原生文档链接见网页阅读关联。
输出
交付可独立阅读的地图文件：范围与阅读问题、职责分区、真实位置、关键协作、来源及限制。技术图（Technical Diagram）表达关系，地图表达职责怎样落到实现，解释文档按阅读问题引用两者。
前后端表达示例
后端订单模块：入口文件解释请求与参数，应用文件解释用例顺序，数据访问文件解释持久化，领域对象解释规则；分别核对真实命名和调用。没有领域层时如实说明，不能生成虚构目录。
前端订单功能：页面文件负责组织阅读与交互，完整业务组件承担表单或列表，客户端文件承接接口，公共组件只有实际复用才列入。说明为何归属该功能，不把所有组件都当成全局共享能力。
示例只是阅读方法。交付时以用户项目的真实文件、规范和调用关系替换抽象名字；来源无法核实时报告相关限制，继续其他有依据的部分。
What ships with it
1 file 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.
- 1mo ago First seen · 35 lines · 33 tokens per session scan A 41732f7bd71c
code-map is a skill published in the GitHub repository BuildrAI/Buildr (28 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,008 once invoked, about $0.0001 per session on Opus 5.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-09-22.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.