Borrowing it
Nothing to install: this file belongs to benoror/obsidianos_work. 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/benoror/obsidianos_work/main/.agents/skills/sprint-retro/SKILL.mdgit clone --depth 1 https://github.com/benoror/obsidianos_workWrote 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/benoror/obsidianos_work/sprint-retro)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/sprint-retro"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/sprint-retro/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/benoror/obsidianos_work/sprint-retro"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/sprint-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 73 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- high System Prompt Leakage · line 146 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00047 | $0.01984 |
| Opus 5.5 | $0.00019 | $0.00794 |
| Sonnet 5.5 | $0.00009 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade A, and why
sprint-retro 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.
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.
Sprint Retro
Synthesize a draft Sprint Retro from everything already in the vault — daily standups, weekly recaps, the sprint planning note, and the previous retro — so the live retro starts from a populated document instead of a blank template.
Usage
/sprint-retro— Infer the current/most-recent sprint from the prior retro + cadence./sprint-retro <N>— Draft the retro for sprint numberN./sprint-retro <dates>— Use an explicit sprint window (e.g.2026-05-19..2026-06-02).
Date Filtering
See date-filter for date-range syntax and parsing.
Output format (mandatory)
Mirror followup-todos — the retro is a bullet document, not a task list:
- Never insert Obsidian Tasks / checkbox lines: no
- [ ],- [x],- [-],- [?]— including in the Action items section. - Never append Tasks date tokens (
📅,🛫,⏳). Write dates inline in prose / ISO (e.g. "by 2026-06-01"). - A single trailing priority emoji (
🔺⏫🔼🔽) as plain text is fine when it reads naturally. - Always use plain list items:
- Description…. Wikilinks ([[@Name]],[[Recap …]]),[PROJ-123](https://…)links, and bold are encouraged.
File naming convention (mandatory)
Sprint artifacts in Meetings/Engineering/Scrum/ follow a single pattern — keep it consistent:
- Retro:
Sprint <N> Retro <YYYY-MM-DD>.md(date = sprint end date / retro day). - Planning:
Sprint <N> Planning <YYYY-MM-DD>.md(date = planning meeting day).
Never leave an undated Sprint N Retro.md or a <Team> - Sprint Planning … variant. If you encounter one while gathering context, flag it and offer to git mv it into the canonical form (updating any [[wikilinks]] that reference the old name).
Workflow
Step 1: Determine sprint number and window
- Verify the current date (see Date Verification in skill-conventions):
date +%F. - List
Meetings/Engineering/Scrum/Sprint * Retro *.mdto find the prior retro (Sprint <N-1> Retro <date>). - Derive this sprint:
- Number = prior + 1 (or the explicit
<N>arg). - Window = the day after the prior retro's end through this sprint's retro day. Retros land on a biweekly cadence (same weekday, ~14 days apart) — extrapolate, then sanity-check against the planning note's date and the scrum dailies present.
- Number = prior + 1 (or the explicit
- Confirm the resolved sprint number and
start..endwindow with the user if anything is ambiguous (missing prior retro, irregular cadence, mid-sprint run).
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.
- 1mo ago First seen · 148 lines · 47 tokens per session scan A 20b7543b58fb
sprint-retro is a skill published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,984 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
mass-ulw
Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only.…
polya-plan
Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).
to-plan
Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).
to-prd
Optional Phase 0.5 of the Pólya Heuristic Coder: Product Requirements Document (PRD) detailing User Stories, SMART Acceptance Criteria, Personas, and Business Goals.
shopify-project-copilot
Continue a Shopify app from its last blocker, inspect local app metadata, hand off decisions, record optional feedback or report progress. Reconcile saved evidence with current files; no background service or deployment authority.