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 srbryers/slope --skill slope-retrogit clone --depth 1 https://github.com/srbryers/slopeWrote 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/srbryers/slope/slope-retro)<a href="https://agentmods.dev/skills/srbryers/slope/slope-retro"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-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/srbryers/slope/slope-retro"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-retro.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.00048 | $0.00445 |
| Opus 5 | $0.00024 | $0.00222 |
| Sonnet 5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
slope-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 9d 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.
What it actually says
SLOPE Post-Merge Retro
Use this after the PR is merged, or when the user asks to preserve lessons from a completed sprint or PR.
Prepare
- Confirm the sprint number from
slope sprint status, the roadmap, the scorecard, or the user. - Capture the merged PR number when available.
- Identify a short summary, durable learnings, hazards, and follow-ups. Do not include secrets or private tokens.
Run
- Preview when details are uncertain:
slope retro post-merge --sprint=<N> --pr=<PR> --summary="<summary>" --learning="<learning>" --dry-run - Persist the retro:
slope retro post-merge --sprint=<N> --pr=<PR> --summary="<summary>" --learning="<learning>" --hazard="<hazard>" --follow-up="<follow-up>" - Repeat
--learning,--hazard, and--follow-upas needed. - Use
--learning=project:8:<text>or another supportedcategory[:weight]:textprefix when the memory category matters. Supported categories areworkflow,style,project,hazard, andother;processis accepted as an alias forworkflow; weight must be 1-10.
Verify
- Check command output for the saved
.slope/retros/post-merge/sprint-N[-pr-M].jsonpath. - Confirm memory persistence with
slope memory search "<distinct learning text>". - If the command reports skipped memories, treat them as duplicate-safe persistence unless the user expected a new learning.
Report
Tell the user the retro path, memory rows added/skipped, and any follow-up work captured. If a follow-up should become roadmap work, add or triage it before ending the phase.
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.
- 9d ago First seen · 34 lines · 48 tokens per session scan A 078841da34eb
slope-retro is a skill published in the GitHub repository srbryers/slope (6 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 445 once invoked, about $0.0002 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
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.