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/miniidealab/openlogos/change-writernpx skills add miniidealab/openlogos --skill change-writergit clone --depth 1 https://github.com/miniidealab/openlogosWrote 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/miniidealab/openlogos/change-writer)<a href="https://agentmods.dev/skills/miniidealab/openlogos/change-writer"><img src="https://agentmods.dev/badge/skills/miniidealab/openlogos/change-writer.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.00000 | $0.01603 |
| Opus 5 | $0.00000 | $0.00801 |
| Sonnet 5 | $0.00000 | $0.00321 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
change-writer 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 6d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Change Writer
辅助填写变更提案——分析变更影响范围，生成结构化的 proposal.md 和按阶段拆解的 tasks.md，确保变更可追溯、影响可控。
触发条件
- 用户刚运行完
openlogos change <slug>并希望 AI 帮忙填写提案 - 用户描述需要修改、新增或删除某个场景/功能
- 用户提到"变更提案"、"change proposal"、"迭代"、"改需求"
前置依赖
- 项目已初始化（
logos/logos.config.json存在） - 变更提案目录已由 CLI 创建（
logos/changes/<slug>/存在） - 主文档可读（
logos/resources/中有已生效的文档）
如果前置条件不满足，提示用户先运行 openlogos change <slug> 创建提案目录。
核心能力
- 理解用户描述的变更意图
- 扫描
logos/resources/中的现有文档，定位受影响范围 - 根据变更传播规则判断变更类型（需求级 / 设计级 / 接口级 / 代码级）
- 生成符合规范的 proposal.md
- 按变更类型自动拆解 tasks.md
执行步骤
Step 1: 理解变更意图
与用户确认以下信息（信息不足则追问，最多 2 轮）：
- 变更是什么：要新增、修改还是删除什么？
- 变更原因：为什么要做这个变更？来自需求反馈、Bug 还是优化？
- 关联场景：涉及哪些已有场景编号（S01, S02...）？
Step 2: 分析影响范围
扫描 logos/resources/ 中的文档，确定影响范围：
- 读取需求文档（
prd/1-product-requirements/），检查相关场景定义 - 读取产品设计（
prd/2-product-design/），检查相关功能规格和原型 - 读取技术方案（
prd/3-technical-plan/），检查相关时序图 - 读取 API 文档（
api/），检查相关端点 - 读取 DB 文档（
database/），检查相关表结构 - 读取编排测试（
scenario/），检查相关测试用例
Step 3: 判断变更类型
参照变更传播规则确定变更类型及最小更新范围：
| 变更类型 | 最少需要更新 |
|---|---|
| 需求级变更 | 全链路（需求 → 设计 → 架构 → API/DB → 编排 → 代码） |
| 设计级变更 | 原型 + 场景 + API/DB + 编排 + 代码 |
| 接口级变更 | API/DB + 编排 + 代码 |
| 代码级修复 | 代码 + 重新验收 |
Step 4: 生成 proposal.md
按以下模板生成，写入 logos/changes/<slug>/proposal.md：
# 变更提案：[变更名称]
## 变更原因
[为什么要做这个变更？来源于哪个需求/反馈/Bug？]
## 变更类型
[需求级 / 设计级 / 接口级 / 代码级]
## 变更范围
- 影响的需求文档：[列表，精确到文件名和章节]
- 影响的功能规格：[列表]
- 影响的业务场景：[场景编号列表]
- 影响的 API：[端点列表]
- 影响的 DB 表：[表名列表]
- 影响的编排测试：[列表]
## 变更概述
[用 1-3 段话概述具体改什么]
Step 5: 生成 tasks.md
根据变更类型和影响范围，自动拆解任务清单。只列出需要更新的阶段：
# 实现任务
## Phase 1: 文档变更
- [ ] 更新需求文档中 S0x 的验收条件
- [ ] 在场景总览表中新增/修改场景
## Phase 2: 设计变更
- [ ] 更新功能规格中 S0x 的交互设计
- [ ] 更新原型
## Phase 3: 技术变更
- [ ] 更新 S0x 的时序图
- [ ] 更新 API YAML
- [ ] **验证 API YAML** — `logos/resources/api/` 下所有文件必须为有效 YAML 且符合 OpenAPI 3.x 规范（所有包含 `:` 或特殊字符的 `description`/`summary` 值必须用双引号包裹）
- [ ] 更新 DB DDL
- [ ] 更新编排测试用例
- [ ] 实现代码变更
Step 6: 引导后续操作（链式驱动）
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.
- 6d ago First seen · 148 lines · 0 tokens per session scan A 22c251b12d28
change-writer is a skill published in the GitHub repository miniidealab/openlogos (71 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,603 tokens. 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…