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/wangqiqi/trae-ai/code-analyzernpx skills add wangqiqi/trae-ai --skill code-analyzergit clone --depth 1 https://github.com/wangqiqi/trae-aiWhat 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.00022 | $0.00427 |
| Opus 5 | $0.00011 | $0.00214 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
code-analyzer 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
代码分析器
描述
这个技能用于分析项目的代码结构，包括项目类型检测、技术栈识别、代码质量评估等。
使用场景
- 新项目启动时，需要了解当前项目的技术栈
- 接手别人的项目时，快速了解项目结构
- 技术选型前，需要了解现有项目的架构
- 定期进行项目健康度检查和代码质量评估
指令
当用户使用这个技能时，你应该：
-
检测项目类型
- 检查
package.json（Node.js）、requirements.txt（Python）、go.mod（Go）等文件 - 分析技术栈（Vue、React、FastAPI、Django 等）
- 检查
-
分析项目结构
- 列出主要目录和关键文件
- 检测依赖关系
- 识别核心业务模块
-
提供改进建议
- 代码结构优化建议
- 潜在问题提示
- 最佳实践推荐
-
输出格式
- 结构化的分析报告
- 清晰的分类和重点高亮
- 可操作的改进建议
示例
输入
"分析一下这个项目的代码结构"
输出
# 项目代码分析报告
## 项目类型
- Vue 3 + Vite + TypeScript
## 技术栈
- 前端：Vue 3, TypeScript, Pinia
- 构建工具：Vite, ESLint, Prettier
- 测试：Vitest, Testing Library
## 建议
1. 添加单元测试覆盖核心业务逻辑
2. 补充 API 文档
3. 优化项目结构，分离组件和工具
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 · 62 lines · 22 tokens per session scan A 678cee5fc94c
code-analyzer is a skill published in the GitHub repository wangqiqi/trae-ai (24 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 427 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
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…