WhyBuddy: Instructions file for Kiro

.kiro/steering/specs-progress-snapshot-2026-05-21.md

WhyBuddy specs-progress-snapshot-2026-05-21.md is an instructions file for Kiro from xiaojilele-glitch/WhyBuddy. It costs 2,346 tokens per session, scanned A, original, MIT.

A progress snapshot for a software project's specification files. It counts completed and incomplete checklist items across project areas and records their overall completion status.

In plain words
What is it for?
Use it to review specification progress, compare completion across groups, and identify areas that still contain unfinished tasks.
Why use it?
It gives a shared, dated view of what work is finished, partly finished, or still waiting.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is xiaojilele-glitch/WhyBuddy's own configuration. It tells Kiro how to work on WhyBuddy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything WhyBuddy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xiaojilele-glitch/WhyBuddy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xiaojilele-glitch/WhyBuddy/main/.kiro/steering/specs-progress-snapshot-2026-05-21.md
Clone the repo
git clone --depth 1 https://github.com/xiaojilele-glitch/WhyBuddy

Made for: Kiro.

Wrote 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.

agentmods badge for WhyBuddy specs-progress-snapshot-2026-05-21.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/specs-progress-snapshot-2026-05-21/github.svg)](https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/specs-progress-snapshot-2026-05-21)
Your own site
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/specs-progress-snapshot-2026-05-21"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/specs-progress-snapshot-2026-05-21/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.

agentmods 80×15 button for WhyBuddy specs-progress-snapshot-2026-05-21.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xiaojilele-glitch/whybuddy/specs-progress-snapshot-2026-05-21"><img src="https://agentmods.dev/badge/instructions/xiaojilele-glitch/whybuddy/specs-progress-snapshot-2026-05-21.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,346 This file is loaded in full into every session.
When invoked 2,346 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02346 $0.02346
Opus 5.5 $0.00938 $0.00938
Sonnet 5.5 $0.00469 $0.00469
Haiku 4.5 $0.00235 $0.00235

Measured 1mo ago against content hash b6d8851c529c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WhyBuddy specs-progress-snapshot-2026-05-21.md 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.

.kiro/steering/specs-progress-snapshot-2026-05-21.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specs 全量进度快照(2026-05-21)

统计口径

  • 统计范围:.kiro/specs 目录下所有 spec 的 tasks.md
  • 统计方式:仅统计 - [x] 与 - [ ] 行,不区分缩进层级
  • 本次扫描时间:2026-05-21

总体数字

维度 数值
Spec 目录总数 275
已完成 (done) 205
部分完成 (partial) 43
未开始 (todo) 26
无 tasks.md 1
总 checklist 项 8218
已勾选项 7133
未勾选项 1085
整体完成率 86.8%

分类统计

分类 Spec 数 Done Partial Todo 任务项完成率
web-aigc-node-* 52 52 0 0 239/239 (100%)
web-aigc-platform-* 6 6 0 0 34/34 (100%)
blueprint-* 13 13 0 0 342/342 (100%)
project-* (Project-first) 10 10 0 0 123/123 (100%)
ui-redesign-* 11 8 3 0 410/418 (98.1%)
autopilot-* 63 50 10 3 2536/2613 (97.1%)
ue-* (Unreal Engine) 20 5 1 14 155/480 (32.3%)
核心与其他 100 61 29 10 3294/3969 (83%)

已封板基线(100% 完成)

以下分类已全部完成,不再作为推进目标:

  • Web-AIGC 节点层:52/52 specs,239/239 任务项
  • Web-AIGC 平台层:6/6 specs,34/34 任务项
  • Blueprint 系列:13/13 specs,342/342 任务项
  • Project-first 系列:10/10 specs,123/123 任务项

近完成分类(>95%)

  • UI Redesign:8/11 done,3 个 partial,完成率 98.1%
  • Autopilot 系列:50/63 done,10 个 partial,3 个 todo,完成率 97.1%

未启动分类

UE (Unreal Engine) 系列:14 个 todo

全部为 0% 完成,属于远期规划:

  • ue-camera-system、ue-director-prompt-system、ue-event-callback-system
  • ue-fallback-and-degradation、ue-interaction-passthrough
  • ue-local-resource-and-session-governance、ue-mobile-lite-viewer
  • ue-multi-user-session-isolation、ue-performance-profiling-and-quality-tier
  • ue-realtime-narration、ue-recording-and-replay-export
  • ue-scene-asset-pipeline、ue-shot-list-planner、ue-state-sync-bridge

平台级远期规划:6 个 todo

  • production-deployment、multi-user-office、multi-tenant-architecture
  • multi-region-disaster-recovery、k8s-agent-operator、edge-brain-deployment

Read the full file on GitHub · 184 lines

Changes

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.

  1. 1mo ago First seen · 184 lines · 2,346 tokens per session scan A b6d8851c529c

Subscribe to this mod's changes

WhyBuddy specs-progress-snapshot-2026-05-21.md is an instructions file published in the GitHub repository xiaojilele-glitch/WhyBuddy (380 stars, last pushed 1mo ago), licensed MIT. It adds 2,346 tokens to every session, about $0.0094 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-09-23.

Related

WhyBuddy specs-progress-snapshot-2026-05-21.md compared with instructions from other repositories

WhyBuddy specs-progress-snapshot-2026-05-21.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
WhyBuddy specs-progress-snapshot-2026-05-21.mdxiaojilele-glitch/WhyBuddyInstructions file3801mo agoMITA2,346Kiro
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode