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.
git clone --depth 1 https://github.com/an8079/take-skillsWrote 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/commands/an8079/take-skills/takes-analyze)<a href="https://agentmods.dev/commands/an8079/take-skills/takes-analyze"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-analyze/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/commands/an8079/take-skills/takes-analyze"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-analyze.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.00027 | $0.00700 |
| Opus 5 | $0.00014 | $0.00350 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
takes-analyze 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 9d 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
/analyze - 分析项目架构
深入分析现有项目，生成详细的架构报告。
使用方式
/analyze [选项]
分析维度
| 维度 | 说明 | 输出 |
|---|---|---|
| 项目结构 | 目录树、文件组织 | 结构图 |
| 技术栈 | 语言、框架、依赖 | 技术列表 |
| 入口点 | 启动文件、入口函数 | 文件列表 |
| 模块关系 | 模块依赖、数据流 | 关系图 |
| API 接口 | 路由定义、接口规范 | 接口清单 |
| 数据模型 | 数据结构、数据库 | 模型图 |
分析流程
-
收集信息
- 扫描项目文件
- 读取配置文件
- 分析依赖关系
-
生成报告
- 输出结构化分析
- 识别关键组件
- 标注潜在风险
-
提供建议
- 开发范围建议
- 架构改进建议
- 安全审查建议
输出示例
═══════════════════════════════════════════════════
📊 项目架构分析报告
═══════════════════════════════════════════════════
📦 项目结构
├── src/
│ ├── api/ # API 路由层
│ ├── services/ # 业务逻辑
│ └── models/ # 数据模型
├── tests/
└── package.json
🛠 技术栈
├── 语言: TypeScript
├── 框架: Express.js
├── 包管理: npm
└── 测试: Jest
🔗 入口点
├── src/index.ts
└── src/app.ts
⚠️ 风险提示
├── 缺少 API 版本控制
├── 部分模块缺少测试
└── 建议添加请求限流
═══════════════════════════════════════════════════
分析模式
| 模式 | 说明 | 适用场景 |
|---|---|---|
| 快速分析 | 基础结构扫描 | 快速了解项目 |
| 完整分析 | 深入代码分析 | 全面理解架构 |
| 安全分析 | 重点检查安全 | 准备开发前 |
| 增量分析 | 只分析新增部分 | 持续维护 |
分析后
/scope show # 查看当前开发边界
/code # 开始边界内开发
注意事项
- 分析结果会缓存，重复分析会更快
- 完整分析可能需要较长时间
- 某些深层分析需要安装依赖
示例
/analyze # 完整分析当前项目
/analyze --quick # 快速扫描
/analyze --security # 安全重点分析
/analyze src/api # 只分析指定目录
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.
- 9d ago First seen · 107 lines · 27 tokens per session scan A d278df7b2e01
takes-analyze is a command published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 700 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.