Borrowing it
Nothing to install: this file belongs to AsiaOstrich/EngramGraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AsiaOstrich/EngramGraph/main/.agents/skills/retrospective-assistant/SKILL.mdgit clone --depth 1 https://github.com/AsiaOstrich/EngramGraphWrote 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/asiaostrich/engramgraph/retrospective-assistant)<a href="https://agentmods.dev/skills/asiaostrich/engramgraph/retrospective-assistant"><img src="https://agentmods.dev/badge/skills/asiaostrich/engramgraph/retrospective-assistant/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/asiaostrich/engramgraph/retrospective-assistant"><img src="https://agentmods.dev/badge/skills/asiaostrich/engramgraph/retrospective-assistant.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.00078 | $0.01630 |
| Opus 5.5 | $0.00031 | $0.00652 |
| Sonnet 5.5 | $0.00016 | $0.00326 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
retrospective 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 14d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective Assistant | 回顧助手
Language: English | 繁體中文
Guide structured team retrospectives to identify improvements and track action items. Support Sprint and Release retrospective types with multiple facilitation techniques.
引導結構化的團隊回顧，識別改善機會並追蹤行動項目。支援 Sprint 和 Release 回顧類型，提供多種引導技法。
Workflow | 工作流程
PREPARE ──► GATHER ──► ANALYZE ──► DECIDE ──► TRACK
準備資料 蒐集意見 分析歸納 決定行動 追蹤落實
Phase 1: PREPARE | 準備
Gather data from git log, metrics, and issue tracker to ground the discussion.
從 git log、指標和 issue tracker 蒐集數據作為討論基礎。
Phase 2: GATHER | 蒐集
Collect perspectives using a structured technique.
使用結構化技法蒐集團隊觀點。
Phase 3: ANALYZE | 分析
Group items and identify patterns.
分組歸納並識別模式。
Phase 4: DECIDE | 決定
Select top 1-3 improvements as action items.
選出前 1-3 項改善作為行動項目。
Phase 5: TRACK | 追蹤
Review previous actions and track new ones.
檢視過去的行動項目並追蹤新項目。
Retrospective Types | 回顧類型
| Type | When | Duration | Focus | 焦點 |
|---|---|---|---|---|
| Sprint | End of iteration | 30-60 min | Process, collaboration, tools | 流程、協作、工具 |
| Release | After release | 60-90 min | Quality, metrics, cross-team | 品質、指標、跨團隊 |
Facilitation Techniques | 引導技法
| Technique | Best For | Structure | 結構 |
|---|---|---|---|
| Start-Stop-Continue | Quick, default | Start / Stop / Continue | 開始 / 停止 / 繼續 |
| Starfish | Nuanced analysis | More / Keep / Less / Start / Stop | 更多 / 保持 / 減少 / 開始 / 停止 |
| 4Ls | Team building | Liked / Learned / Lacked / Longed for | 喜歡 / 學到 / 缺少 / 渴望 |
| Sailboat | Visual, creative | Wind / Anchor / Rocks / Island | 風 / 錨 / 礁石 / 島嶼 |
Commands | 指令
| Command | Action | 說明 |
|---|---|---|
/retrospective |
Interactive Sprint retrospective (default) | 互動式 Sprint 回顧 |
/retrospective sprint |
Sprint retrospective | Sprint 回顧 |
/retrospective release |
Release retrospective with metrics | Release 回顧（含指標） |
/retrospective actions |
List open action items | 列出未完成行動項目 |
/retrospective --technique starfish |
Use specific technique | 使用指定技法 |
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.
- 14d ago First seen · 154 lines · 78 tokens per session scan A 6e4816981e09
retrospective is a skill published in the GitHub repository AsiaOstrich/EngramGraph (3 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,630 once invoked, about $0.0003 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-10-16.
Other skills, from other repositories
kivgraph
Use Kivgraph's local MCP server to search symbols, read their source, and follow references, dependencies, cross-repository consumers and graph status in the indexed code graph.
mushroom
Live graph memory for agents — query and create entities, derive relationships by rule, explain why two things are associated, read the graph at a past commit, ask what a change would do, and answer as one role. Trigger on: memory, remember, recall, relationship, entity, association, why are X and Y related, as of…
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
wenlan-handoff
End a work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /wenlan-handoff.
wenlan-brief
Read the current Space-owned project Brief from Wenlan. With an optional topic, appends separately labeled related context from the same Space. Invoked as /wenlan-brief [topic] when resuming work or asking to catch up.
sibyl
Persistent memory and task coordination for this project. Invoke for any prompt about past work, project state, in-progress tasks, prior decisions, gotchas, or capturing a non-obvious learning. Also covers semantic search across project knowledge and external docs.