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 agentmods add skills/joa23/linear-cli/retronpx skills add joa23/linear-cli --skill retrogit clone --depth 1 https://github.com/joa23/linear-cliWhat 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 | $0.00025 | $0.00750 |
| Opus 5 | $0.00013 | $0.00375 |
| Sonnet 5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro Skill - Sprint Retrospective
You are an expert at analyzing completed sprints and generating actionable retrospective insights.
When to Use
Use this skill when:
- A sprint/cycle has ended
- Preparing for a retrospective meeting
- Analyzing team performance trends
Process
-
Gather Cycle Data
linear cycles analyze --team ENG --count 3 linear cycles get CYCLE-ID -
Analyze Completion
- Planned vs actual completion
- Scope changes during cycle
- Carry-over items
-
Identify Patterns
- Estimation accuracy
- Blocker frequency
- Category distribution
-
Generate Insights
Analysis Areas
Velocity & Completion
- Points planned vs completed
- Issue count planned vs completed
- Completion rate trend
Scope Management
- Issues added mid-cycle
- Issues removed/deferred
- Scope creep percentage
Blockers & Dependencies
- Issues that were blocked
- Average time blocked
- Dependency-related delays
Workload Distribution
- Points per team member
- Completion rate by assignee
- Bottleneck identification
Output Format
RETROSPECTIVE: Cycle 23
════════════════════════════════════════
SUMMARY
────────────────────────────────────────
Planned: 40 points (12 issues)
Completed: 34 points (10 issues)
Completion Rate: 85%
SCOPE CHANGES
────────────────────────────────────────
Added mid-cycle: 3 issues (8 pts)
Removed: 1 issue (2 pts)
Carried over: 2 issues (6 pts)
Scope creep: 15%
WHAT WENT WELL
────────────────────────────────────────
+ Auth refactor completed ahead of schedule
+ Zero critical bugs in production
+ Good collaboration on API work
WHAT COULD IMPROVE
────────────────────────────────────────
- 2 issues blocked for 3+ days (ENG-201, ENG-203)
- Underestimated ENG-205 (3pts planned, 8pts actual)
- Late scope additions disrupted focus
TRENDS (3 cycles)
────────────────────────────────────────
Velocity: 34 → 32 → 34 (stable)
Completion: 85% → 88% → 85% (stable)
Scope creep: 12% → 8% → 15% (increasing)
ACTION ITEMS
────────────────────────────────────────
1. Add buffer for complex API work
2. Daily standup check on blockers
3. Scope freeze after day 2
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.
- 2d ago First seen · 135 lines · 25 tokens per session scan A bfc5c2d33917
retro is a skill published in the GitHub repository joa23/linear-cli (141 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 750 once invoked, about $0.0001 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-30.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.