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 asherzj/ashers-agent-skills --skill flow-architecture-maintenancegit clone --depth 1 https://github.com/asherzj/ashers-agent-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/skills/asherzj/ashers-agent-skills/flow-architecture-maintenance)<a href="https://agentmods.dev/skills/asherzj/ashers-agent-skills/flow-architecture-maintenance"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/flow-architecture-maintenance/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/asherzj/ashers-agent-skills/flow-architecture-maintenance"><img src="https://agentmods.dev/badge/skills/asherzj/ashers-agent-skills/flow-architecture-maintenance.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.00053 | $0.00994 |
| Opus 5 | $0.00026 | $0.00497 |
| Sonnet 5 | $0.00011 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
flow-architecture-maintenance 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 12d 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
架构维护交付流程
本流程负责完成一次独立的架构优化迭代：保持既有外部行为，在划定范围内深化模块、收缩接口并删除旧结构。它组合 improve-codebase-architecture、to-spec、to-tickets、implement 和 context-gc，不复制它们的内部操作。
开始前读取仓库的 AGENTS.md 或 CLAUDE.md、领域上下文、相关 ADR、架构约束和当前工单规则。首次在仓库中运行工程流程前，应先完成 setup-engineering-skills。
入口门禁
只有存在具体摩擦证据时使用，例如：
- 热点文件反复跨模块修改；
- 调用方需要知道过多顺序、错误或配置细节；
- 同一领域规则散落在多个调用点；
- 浅模块、假接缝或重复 Adapter 增加导航成本；
- 临时兼容路径已经达到删除条件；
- 当前接口使关键行为难以从公共接缝验证。
“以后也许会需要”不是充分证据。用户只是想增加业务能力时，转用 flow-feature 或 flow-large-effort。
1. 扫描并选择一个热点
调用 improve-codebase-architecture，让用户从报告中选择一个候选。本轮只处理一个架构热点；其他候选保留为报告或独立工单，不一起实现。
选择后明确：
- 当前摩擦的证据；
- 必须保持的外部行为和性能特征；
- 允许修改的模块和接缝；
- 明确禁止扩大的业务范围；
- 预期删除、合并或隐藏的复杂度。
如果设计要求新增领域职责、改变数据所有权或扩大产品承诺，停止本流程，把它转成新需求决策。
2. 形成架构维护规格
调用 to-spec。规格中的用户视角改为调用方和维护者视角，并额外包含：
- 行为不变量和现有验收证据；
- 当前接口与目标接口；
- 删除清单；
- 迁移和回滚策略；
- 架构约束验证；
- 临时扩展形式的退出条件。
规格不能以新增功能证明价值；价值来自局部性、杠杆、可测试性或删除的复杂度。
3. 拆迁移工单
调用 to-tickets。普通重构仍按可保持绿色的纵向切片拆分；宽重构使用 expand–migrate–contract：
- 扩展新形式而不破坏旧调用方；
- 按可独立验证的影响面迁移；
- 删除旧形式和临时兼容；
- 运行最终集成与架构验证。
删除工单不能省略。用户确认阻塞边时，同时确认哪张工单负责让旧结构真正消失。
4. 逐工单实现
每次在干净上下文中对一张无阻塞工单调用 implement。重构测试通过既有公共接缝验证行为；新接口处的测试建立后，删除绑定旧内部结构的重复测试，不把两套测试永久叠加。
任何工单发现必须改变产品语义时立即停止，并回到规格或范围决策，不用“重构需要”掩盖需求变化。
5. 回收上下文并完成
所有迁移和删除工单完成后调用 context-gc，并运行仓库已有的架构、契约、单元、集成和必要端到端验证。
完成条件：
- 既有验收行为保持成立；
- 旧接口、旧实现和临时兼容已经按规格删除；
- 模块接口更小，调用方需要知道的事实更少；
- 没有新增业务范围或未授权依赖；
- 领域文档、ADR 和架构说明与当前实现一致；
- 仓库规定的项目管理记录已经更新。
最终汇报删除了什么复杂度、验证了哪些不变量、剩余风险和全部交付指针。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 84 lines · 53 tokens per session scan A b26d75fd2323
flow-architecture-maintenance is a skill published in the GitHub repository asherzj/ashers-agent-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 53 tokens to every session and 994 once invoked, about $0.0003 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
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…