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 jianchen08/Agent-os-open --skill skill-solution-researchgit clone --depth 1 https://github.com/jianchen08/Agent-os-openWrote 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/jianchen08/agent-os-open/skill-solution-research)<a href="https://agentmods.dev/skills/jianchen08/agent-os-open/skill-solution-research"><img src="https://agentmods.dev/badge/skills/jianchen08/agent-os-open/skill-solution-research.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.00047 | $0.02019 |
| Opus 5 | $0.00023 | $0.01009 |
| Sonnet 5 | $0.00009 | $0.00404 |
| Haiku 4.5 | $0.00005 | $0.00202 |
Grade A, and why
研究方案规划 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 yesterday.
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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
研究方案规划
本技能是流程指引，不是逐条打勾清单：按场景判断使用，遇不适用情况保持裁量，不机械执行。
描述
研究类/调研分析类项目的方案规划技能。提供调研框架、研究方法论、分析维度、综合论证等研究领域特有要素的方案设计指导。替代统一模板中的通用章节，按学术研究和专业调研的维度组织方案内容。
适用场景
- 深度研究/复杂分析项目的方案规划阶段
- 调研框架设计、方法论选择的方案产出
- 市场调研/技术调研/学术研究/竞品分析等方向
方案内容框架
一、研究目标与范围
明确研究的核心导向：
| 维度 | 说明 | 示例 |
|---|---|---|
| 研究目标 | 核心研究问题或决策需求 | "评估3种分布式数据库在微服务架构下的适用性" |
| 研究类型 | 探索性/描述性/解释性/评估性 | 根据目标选择类型 |
| 范围边界 | 研究覆盖和排除的范围 | "只考虑开源方案，排除商业方案" |
| 预期产出 | 最终交付物形式 | 调研报告、对比矩阵、推荐方案 |
| 决策者 | 研究成果的受众和决策层级 | 技术负责人/产品经理/管理层 |
二、调研框架设计
定义调研的方法论和框架：
| 维度 | 说明 |
|---|---|
| 调研维度 | 从哪些维度进行对比分析（功能/性能/成本/生态/学习曲线等） |
| 评估标准 | 每个维度的评判标准和权重 |
| 数据来源 | 一手数据（实验/问卷/访谈）和二手数据（文档/社区/白皮书） |
| 样本范围 | 调研对象的选取范围和数量 |
| 时间窗口 | 调研的时间范围和数据时效性要求 |
常见调研框架：
-
技术调研框架：
- 功能覆盖度 → 性能指标 → 生态成熟度 → 运维成本 → 学习曲线
- 辅助：POC验证、基准测试
-
市场调研框架：
- 市场规模 → 竞品格局 → 用户需求 → 商业模式 → 进入壁垒
- 辅助：SWOT分析、波特五力
-
学术研究框架：
- 文献综述 → 理论框架 → 研究方法 → 数据分析 → 结论建议
- 辅助：假设验证、定量/定性分析
三、方法论选择
| 方法论 | 适用场景 | 优势 | 劣势 |
|---|---|---|---|
| 系统文献综述 | 学术研究、技术前沿追踪 | 全面、可复现 | 耗时、可能滞后 |
| 对比分析 | 技术选型、方案评估 | 直观、决策导向 | 维度选择影响结果 |
| 案例研究 | 深度理解特定对象 | 深入、context-rich | 难以泛化 |
| 实证研究 | 验证假设、测量效果 | 客观、可信度高 | 实验设计复杂 |
| 专家访谈 | 行业洞察、前沿判断 | 深度、前瞻性 | 主观性强 |
| 问卷调查 | 用户研究、需求收集 | 规模化、量化 | 设计偏差风险 |
四、分析维度与数据需求
根据研究目标定义具体的分析维度：
研究问题：{核心问题}
维度1: {维度名称}
├── 子维度1.1: {具体分析项}
├── 子维度1.2: {具体分析项}
├── 数据来源: {如何获取}
└── 分析方法: {如何分析}
维度2: {维度名称}
└── ...
数据来源清单（方案阶段列出，执行阶段采集）：
| 数据类型 | 来源 | 采集方式 | 可靠度 |
|---|---|---|---|
| 官方文档 | 产品官网/技术文档 | 网页抓取/手动查阅 | ★★★★★ |
| 社区讨论 | GitHub/论坛/StackOverflow | 关键词搜索 | ★★★ |
| 基准测试 | 自有/第三方数据 | 实验运行/查阅报告 | ★★★★ |
| 行业报告 | Gartner/IDC/分析机构 | 付费/公开摘要 | ★★★★ |
五、产出物规划
研究类方案的核心产出物：
| 产出物 | 内容 | 受众 |
|---|---|---|
| 调研报告 | 完整的研究过程和结果 | 决策者、执行者 |
| 对比矩阵 | 多方案的维度对比（表格形式） | 决策者 |
| 推荐方案 | 基于权重的综合推荐 | 决策者 |
| 数据附录 | 原始数据、详细分析过程 | 执行者 |
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.
- yesterday Changed · -6 lines 035e5f091573
- 6d ago First seen · 161 lines · 47 tokens per session scan A c03736258cbf
研究方案规划 is a skill published in the GitHub repository jianchen08/Agent-os-open (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,019 once invoked, about $0.0002 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
agent-tool
Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.aiframework }}.
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
channel-bot
Work with messaging-channel bots (Telegram / Slack) — register a bot, route inbound messages through the AI agent, handle webhooks vs polling, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.