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 zyx379/zoehis_workflow --skill zoehis-code-mapgit clone --depth 1 https://github.com/zyx379/zoehis_workflowWrote 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/zyx379/zoehis_workflow/zoehis-code-map)<a href="https://agentmods.dev/skills/zyx379/zoehis_workflow/zoehis-code-map"><img src="https://agentmods.dev/badge/skills/zyx379/zoehis_workflow/zoehis-code-map.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.1 | $0.00083 | $0.02435 |
| Opus 5 | $0.00042 | $0.01218 |
| Sonnet 5 | $0.00017 | $0.00487 |
| Haiku 4.5 | $0.00008 | $0.00244 |
Grade A, and why
zoehis-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 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZOEHIS 代码地图（需求分析阶段）
在 Step 4 需求分析 为复杂需求或跨仓改动建立「代码地图」，供 Step 5 spec 与 Step 6 实现使用。
何时使用
- workflow Step 4（复杂需求必做；Standard 可简化为文件清单 + 一行调用关系）
- 外部编辑器（Trae/CodeBuddy）做初步分析时，按本 Skill 输出格式交接给 Cursor
- Codegraph 不可用或未索引时，本 Skill 为首选定位手段
子仓库定位（关键）
所有子仓库均位于工作区根目录下（如
d:\zoe_work_space\fj-common\onelink-web-pres-fj-common）。 禁止用 Glob**/{repo-name}/**搜索子仓库（会返回空）。 正确方式：直接LS {workspaceRoot}/{repo-name}/或Read {workspaceRoot}/{repo-name}/pages/...。
| 仓库 | 域 | 实际路径 |
|---|---|---|
| onelink-web-outp-fj-common | 门诊前端 | {workspaceRoot}/onelink-web-outp-fj-common/ |
| onelink-web-pres-fj-common | 医嘱前端 | {workspaceRoot}/onelink-web-pres-fj-common/ |
| onelink-web-his-charge-fj-common | 收费前端 | {workspaceRoot}/onelink-web-his-charge-fj-common/ |
| onelink-web-his-drug-fj-common | 药库前端 | {workspaceRoot}/onelink-web-his-drug-fj-common/ |
| onelink-web-his-fj-component | 公共组件 | {workspaceRoot}/onelink-web-his-fj-component/ |
| onelink-web-cis-common | CIS 公共组件 | {workspaceRoot}/onelink-web-cis-common/ |
| onelink-micro-pres-fj-common | 医嘱后端 | {workspaceRoot}/onelink-micro-pres-fj-common/ |
| onelink-micro-charge-fj-common | 收费服务 | {workspaceRoot}/onelink-micro-charge-fj-common/ |
| onelink-micro-optimus-fj-common | 基础服务 | {workspaceRoot}/onelink-micro-optimus-fj-common/ |
| onelink-micro-insurance-fj-ybcommon | 医保服务 | {workspaceRoot}/onelink-micro-insurance-fj-ybcommon/ |
收集顺序（按优先级）
线索优先原则：必须严格按以下顺序执行，禁止跳过线索直接 Glob 搜索。 每一步必须产出明确结论后才能进入下一步。
0. 提取线索（必做，第一步）
从 prompt 模板中提取所有可用线索，按优先级排序：
| 优先级 | 线索来源 | 示例 | 直接动作 |
|---|---|---|---|
| P0 | 已知线索（git 标题/commit 信息） | [XXX]【福州市第一总院】医嘱申请条数展示与页面展示不一致问题系停嘱时间与执行时间问题 |
提取关键词 → 直接 Grep 定位 |
| P1 | 需求描述中的页面/功能名 | 医嘱申请、停嘱时间 |
映射到子仓库 → 直接 Read 对应文件 |
| P2 | 截图/报错信息 | 截图中的组件名、URL、接口名 | 直接定位对应 Vue/JS/Dao.xml |
| P3 | 疑似线索 | 用户提供的表名、接口名 | 直接 Read 验证 |
| P4 | 禅道号/项目名 | 203656、漳州市医院 |
检索记忆库找类似 case |
| P5 | 路径约定 | pages/{camelCase}/、api/{kebab-service}/ |
按约定路径直接 Read |
| P6 | 定向 Grep | 类名/方法名/路由 | 小范围 Grep（带仓库前缀） |
| P7 | Codegraph（可选） | 符号名明确时 | codegraph_explore 补全调用链 |
| P8 | MCP 字段核验（按需） | 涉及表名/SQL 列时 | get_table_schema 核验 |
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.
- 7d ago First seen · 162 lines · 83 tokens per session scan A d069fa67e764
zoehis-code-map is a skill published in the GitHub repository zyx379/zoehis_workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 2,435 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…