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/jianchen08/agent-os-open/skill-solution-softwarenpx 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.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 | $0.00043 | $0.02760 |
| Opus 5 | $0.00022 | $0.01380 |
| Sonnet 5 | $0.00009 | $0.00552 |
| Haiku 4.5 | $0.00004 | $0.00276 |
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 4d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
软件方案规划
领域需求与流程调研
进入方案设计前，先调研软件项目的需求与约束，确保方案只锁定"有真实权衡的关键决策"，把无权衡的细节推迟到执行阶段（依据 Google Design Doc 实践）。
| 调研维度 | 要搞清的问题 | 调研方式 |
|---|---|---|
| 需求来源与背景 | 是新项目、功能新增、重构还是 Bug 修复？需求方是产品/技术/用户反馈？需求来源是 PRD、User Story、技术债还是合规要求？[依据: Atlassian PRD / Google Design Doc] | 派发 research_agent + 与用户澄清 |
| 现有上下文 | 是否有现成代码/架构？技术栈是什么？哪些必须复用、哪些可替换？遗留约束（历史决策、外部依赖）有哪些？系统上下文边界在哪？[依据: arc42 §3 Context / Google Design Doc §1] | file_read 现有 .project/ 文档与代码结构 |
| 目标与非目标 | Goals（做什么）和 Non-goals（本可以做但明确不做的事）是什么？非目标不是"不要崩溃"，而是"本可以做但选择不做"，用于防止范围蔓延。[依据: Google Design Doc] | 与用户讨论确认 |
| 非功能需求(NFR) | 性能、可用性、安全、可扩展性等质量属性——每个量化到可验证场景（刺激源→刺激→响应→响应度量）。NFR 是架构约束，直接限制设计决策。[依据: ATAM / Red Hat NFR / arc42 §2] | 派发 research_agent + 用户确认 |
| 技术约束 | 必须用/不能用的技术栈？必须集成的遗留系统/外部依赖？部署环境约束？[依据: arc42 §2 Constraints] | 与用户确认 |
| 关键决策点 | 哪些决策"有真实权衡可言"（值得写 design doc / ADR）？哪些明显无权衡（该直接写代码）？[依据: Google Design Doc / ADR(Nygard)] | 与用户讨论 |
调研产出：调研报告引用写入方案总纲；关键约束和架构决策写入 .project/（架构约束→architecture.md，功能边界→features.md，决策记录→ ADR 形式附于 architecture.md）。
方案内容框架
一、架构设计
系统整体架构必须明确以下维度：
| 维度 | 说明 | 决策方式 |
|---|---|---|
| 分层架构 | 系统层次划分（展示层/业务层/数据层/基础设施层等） | 根据复杂度选择分层数 |
| 模块划分 | 按业务领域划分子模块，明确各模块职责边界 | 领域驱动/功能聚合 |
| 数据流 | 模块间的数据流动方向、数据格式、传输方式 | 根据耦合要求选择 |
| 部署架构 | 服务部署方式、环境划分、基础设施依赖 | 根据规模和可用性要求选择 |
架构设计原则：
- 关注点分离：各模块职责单一，高内聚低耦合
- 可演化性：架构支持增量演进，避免过度设计
- 约定优于配置：标准化接口和通信方式
- 防御性设计：考虑异常情况、错误边界和降级策略
二、技术选型
技术选型的方案中应包含对比分析：
| 决策点 | 备选方案 | 评估维度 | 推荐方案 |
|---|---|---|---|
| 语言/运行时 | 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等 | 语言匹配、社区活跃度 | — |
技术选型原则：
- 成熟优先：优先选择经过验证的成熟技术栈
- 约束适配：符合项目的技术约束和遗留系统兼容性
- 生态完整：文档、社区、第三方库支持要好
- 避免锁定：关键决策点避免绑定特定供应商
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.
- 4d ago First seen · 168 lines · 43 tokens per session scan A 5bd0d6e7b550
软件方案规划 is a skill published in the GitHub repository jianchen08/Agent-os-open (5 stars, last pushed 9d ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,760 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
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 }}.
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.
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 }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.