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/lync-cyber/cataforge/project-visualizationnpx skills add lync-cyber/CataForge --skill project-visualizationgit clone --depth 1 https://github.com/lync-cyber/CataForgeWhat 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.00155 | $0.01057 |
| Opus 5 | $0.00077 | $0.00528 |
| Sonnet 5 | $0.00031 | $0.00211 |
| Haiku 4.5 | $0.00015 | $0.00106 |
Grade A, and why
project-visualization 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 3d 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
项目可视化 (project-visualization)
把框架内既有的结构化数据渲染为可读图形。viz 不造数据、不做内容决策,只在 KG / doc-index / EVENT-LOG / CORRECTIONS / agent-skill 资产之上做薄渲染,经 cataforge viz <视图> CLI 调用。
能力边界
- 能做: 渲染追溯链、覆盖矩阵、依赖图、编排拓扑、阶段进度、时间线、腐化趋势为图/时间线/指标
- 不做: 不查实体属性(走
cataforge kg query/cataforge context read)、不出审查 verdict(走 code-review / doc-review / framework-review)、不写业务数据
输入规范
按"想看什么"选视图（先用 cataforge viz status 看哪些视图当前有数据），可选 --format mermaid|dot|json / --html / -o PATH / 各视图过滤参数:
| 想看什么 | 命令 |
|---|---|
| 项目健康 KPI(阶段/文档/覆盖/断链/腐化,默认 json) | cataforge viz overview |
| 编排拓扑 orchestrator→phase→agent→skill | cataforge viz framework |
| agent / skill / rules 资产目录(元数据+体量+依赖图,--html 出可搜索面板) | cataforge viz assets |
| 需求→模块→任务→测试追溯链 / 断链 | cataforge viz trace [实体ID] |
| Feature 实现 / 测试覆盖盲区 | cataforge viz coverage |
| 架构模块依赖图 | cataforge viz arch |
| 文档依赖图(stale / 断链高亮) | cataforge viz docs |
| 任务 DAG + 关键路径 | cataforge viz tasks |
| SDLC 阶段进度 + 门禁状态 | cataforge viz phase |
| EVENT-LOG 时间线 | cataforge viz timeline |
| 纠偏 / 腐化趋势 | cataforge viz decay |
| 全视图聚合健康度看板 | cataforge viz dashboard |
输出规范
- 默认文本:
--format mermaid|dot|json,GitHub / IDE / 文档站原生渲染,可-o PATH内联进文档 - 交互页:
--html产单文件离线 HTML(图用 Cytoscape.js、看板用 ECharts),零外链可断网打开 - 本地看板:
cataforge viz quickstart一键生成 + 本地服务 + 开浏览器 + 源变更自动重生成（浏览器刷新可见）
Anti-Patterns
- 禁止: 手写 mermaid 依赖图嵌进 dev-plan — 应跑
cataforge viz tasks --format mermaid,同一图算法产出,手写易与关键路径标注漂移 - 禁止: 把 viz 当数据源去查实体属性 — 结构化查询走
cataforge kg query/cataforge context read,viz 只渲染既有数据 - 禁止: 用 viz 产物替代质量门禁结论 — 覆盖图能暴露盲区但不出 verdict,审查结论仍由 code-review / doc-review 给出
- 避免: 无视空数据源直接跑视图 — KG / EVENT-LOG 未就绪时先
cataforge viz status再选有数据的视图
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.
- 3d ago First seen · 47 lines · 155 tokens per session scan A c8aeef79a00e
project-visualization is a skill published in the GitHub repository lync-cyber/CataForge (128 stars, last pushed 1mo ago), licensed MIT. It adds 155 tokens to every session and 1,057 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…