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-softwaregit 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-software)<a href="https://agentmods.dev/skills/jianchen08/agent-os-open/skill-solution-software"><img src="https://agentmods.dev/badge/skills/jianchen08/agent-os-open/skill-solution-software/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/skills/jianchen08/agent-os-open/skill-solution-software"><img src="https://agentmods.dev/badge/skills/jianchen08/agent-os-open/skill-solution-software.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.00043 | $0.02260 |
| Opus 5.5 | $0.00017 | $0.00904 |
| Sonnet 5.5 | $0.00009 | $0.00452 |
| Haiku 4.5 | $0.00004 | $0.00226 |
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 1mo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
软件方案规划
本技能是流程指引，不是逐条打勾清单：按场景判断使用，遇不适用情况保持裁量，不机械执行。
描述
软件开发类项目的方案规划技能。提供架构设计、技术选型、模块划分、接口设计、数据模型等软件工程特有要素的方案设计指导。替代统一模板中的通用章节，按软件工程的专业维度组织方案内容。
适用场景
- 软件开发/代码项目的方案规划阶段
- 架构设计、技术选型的方案产出
- 前端/后端/全栈/桌面端/移动端项目的领域适配
方案内容框架
一、架构设计
系统整体架构必须明确以下维度：
| 维度 | 说明 | 决策方式 |
|---|---|---|
| 分层架构 | 系统层次划分（展示层/业务层/数据层/基础设施层等） | 根据复杂度选择分层数 |
| 模块划分 | 按业务领域划分子模块，明确各模块职责边界 | 领域驱动/功能聚合 |
| 数据流 | 模块间的数据流动方向、数据格式、传输方式 | 根据耦合要求选择 |
| 部署架构 | 服务部署方式、环境划分、基础设施依赖 | 根据规模和可用性要求选择 |
架构设计原则：
- 关注点分离：各模块职责单一，高内聚低耦合
- 可演化性：架构支持增量演进，避免过度设计
- 约定优于配置：标准化接口和通信方式
- 防御性设计：考虑异常情况、错误边界和降级策略
二、技术选型
技术选型的方案中应包含对比分析：
| 决策点 | 备选方案 | 评估维度 | 推荐方案 |
|---|---|---|---|
| 语言/运行时 | Python/Node.js/Go/Java/Rust等 | 团队能力、生态成熟度、性能要求 | — |
| Web框架 | FastAPI/Express/Spring/Flask等 | 开发效率、性能、生态 | — |
| 数据库 | PostgreSQL/MySQL/MongoDB/Redis等 | 数据模型、一致性要求、查询模式 | — |
| 前端框架 | React/Vue/Svelte/Next.js等 | 团队经验、项目规模、SSR需求 | — |
| 部署方式 | Docker/K8s/Serverless/VPS | 运维能力、成本、扩展性要求 | — |
| 测试框架 | Pytest/Vitest/Jest/Playwright等 | 语言匹配、社区活跃度 | — |
技术选型原则：
- 成熟优先：优先选择经过验证的成熟技术栈
- 团队适配：考虑团队现有技术积累
- 生态完整：文档、社区、第三方库支持要好
- 避免锁定：关键决策点避免绑定特定供应商
三、模块与接口设计
将系统拆分为可独立执行的模块，定义模块间接口：
| 模块 | 职责 | 内部结构 | 对外接口 | 依赖 |
|---|---|---|---|---|
| 模块A | 核心职责描述 | 子组件划分 | REST/GraphQL/Event API | 依赖B |
| 模块B | 核心职责描述 | 子组件划分 | 提供接口说明 | 无 |
接口设计规范：
- RESTful 规范：资源命名、HTTP方法、状态码统一
- 输入验证：Schema定义、参数校验规则
- 错误处理：统一错误格式、错误码定义
- 版本控制：API版本策略（URL路径/Header/参数）
四、数据模型
数据结构设计，方案中定义核心实体：
实体：User
├── id: UUID (PK)
├── username: string (unique)
├── email: string
├── password_hash: string
├── role: enum [admin, user, viewer]
├── created_at: datetime
└── updated_at: datetime
实体：Project
├── id: UUID (PK)
├── name: string
├── owner_id: UUID → FK(User.id)
└── status: enum [active, archived]
数据模型原则：
- 范式化：减少数据冗余，保持一致性
- 可索引：核心查询字段设计合理索引
- 可扩展：预留扩展字段或机制
- 审计记录：关键变更记录时间戳和操作人
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.
- 1mo ago Changed f231bbca21ef
- 1mo ago Changed · +6 lines 39a782b38d0c
- 1mo ago First seen · 168 lines · 43 tokens per session scan A 5bd0d6e7b550
软件方案规划 is a skill published in the GitHub repository jianchen08/Agent-os-open (7 stars, last pushed 11d ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,260 once invoked, about $0.0002 per session on Opus 5.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
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 }}.
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.
gitlab_write
Create, modify resources in GitLab. Use gitlabapi for everything.
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 }}.
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.