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 grasscaograss/AwesomeWeldoneSkills --skill periodic-reviewgit clone --depth 1 https://github.com/grasscaograss/AwesomeWeldoneSkillsWrote 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/grasscaograss/awesomeweldoneskills/periodic-review)<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/periodic-review"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/periodic-review/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/grasscaograss/awesomeweldoneskills/periodic-review"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/periodic-review.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.00089 | $0.01474 |
| Opus 5 | $0.00044 | $0.00737 |
| Sonnet 5 | $0.00018 | $0.00295 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
periodic-review 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 11d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Periodic Review
Quick start
/periodic-review → default: previous calendar month
/periodic-review 2026-05 → specific month
/periodic-review 2026 → full year (Jan–Dec)
Workflow
1. Determine time range
- No argument: previous calendar month
YYYY-MM: that specific monthYYYY: January–December of that year
2. Collect materials (parallel)
Run these collections simultaneously:
| Source | Method | Purpose |
|---|---|---|
| Records | List files under archive/records/ with date within range |
设计决策和实现记录 |
| Git log | git log --after=<start> --before=<end> --oneline --stat |
变更统计 |
| Knowledge | List files under archive/knowledge/ modified in range, grouped by subdirectory |
领域知识演进 |
| ADRs | Files under archive/adr/ or docs/adr/ created or modified in range |
架构决策 |
3. Domain-grouped knowledge collection
Knowledge 目录按领域子文件夹组织。统计每个领域的变化情况：
archive/knowledge/
├── dual-arm/ 双臂系统
├── weld-template/ 焊接模板
├── weld-seam/ 焊缝规划
├── coarse-positioning/ 粗定位
├── scanning/ 精定位与扫描
├── capacity/ 产能统计
├── weld-tracking/ 焊接跟踪
├── coordinate/ 坐标与矩阵
├── workflow/ 状态机与工作流
├── frontend/ 前端界面
├── device-robot/ 设备与机器人
└── tools/ 工具与其他
对每个领域子文件夹，收集以下信息：
- 当前文件数 — 列出目录下所有
.md文件 - 期内的变化 — 通过
git log --diff-filter=ACDMR -- <path>获取新增(A)、修改(M)、删除(D)、重命名(R)的文件 - 变化摘要 — 读取每个变更文件的 TL;DR 行（标题后的 blockquote）
4. Domain health assessment
对每个领域计算健康指标：
| 指标 | 阈值 | 状态 |
|---|---|---|
| 文件数 ≤ 5 | 基线 | — |
| 文件数 > 10 | 可能膨胀 | ⚠️ Bloat |
| 文件数 > 15 | 强烈建议拆分 | 🔴 Oversized |
| 期内新增 > 3 | 快速增长 | 📈 Growth |
| 期内无变化 | 稳定 | Stable |
| 单文件目录 | 疏离 | ⚠️ Isolated |
5. Deep analysis for active domains
对期内变化 ≥ 3 个文件的领域，spawn 一个子 agent 进行深度分析：
Prompt 模板：
分析 archive/knowledge/<domain>/ 目录下近期（<period>）的变化趋势。
读取该目录下所有文件的 TL;DR，结合 archive/records/ 中与该领域相关的记录。
回答：
1. 这个领域在做什么方向上的演进？
2. 是否有反复修改同一概念的情况？（暗示设计不稳定）
3. 是否有知识碎片化的迹象？（多个文件描述同一子主题）
4. 对该领域的下一步建议。
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.
- 11d ago First seen · 167 lines · 89 tokens per session scan A 458adcfe967f
periodic-review is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,474 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.