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.
git 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/commands/srbryers/slope/wrap-session)<a href="https://agentmods.dev/commands/srbryers/slope/wrap-session"><img src="https://agentmods.dev/badge/commands/srbryers/slope/wrap-session/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/commands/srbryers/slope/wrap-session"><img src="https://agentmods.dev/badge/commands/srbryers/slope/wrap-session.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.00000 | $0.00408 |
| Opus 5.5 | $0.00000 | $0.00163 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
wrap-session 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.
What it actually says
Wrap Session — Close Out the Working Session
Run the session-close routine. A session is not a sprint: a long session can span several sprints or end mid-sprint, so this complements /post-sprint rather than replacing it. Leaked claims and unpushed work are the two failure modes this prevents.
Steps
1. Generate the standup wrap
Run slope standup — it reports sprint + scorecard state, branch + commits this session, transcript volume, blockers, and decisions. This is the body of your handoff summary.
2. Check for unpushed work
The last push is the recovery point. Run:
git status --short— uncommitted changes? Commit them (use awip:prefix if incomplete).git log @{upstream}..HEAD --oneline 2>/dev/null || git log origin/main..HEAD --oneline— unpushed commits? Push the branch.
Never end a session with uncommitted or unpushed work.
3. Report sprint state
slope sprint status— if gates are pending, say which ones in the handoff.- For every sprint touched this session, confirm
docs/retros/sprint-N.jsonexists or note that the scorecard is missing. slope status— check for dangling workflow executions or stale claims that would gate the next session.
4. End the session
Run slope session end — with one active session it defaults to it; this releases the session's claims. Leaked claims block later sessions.
5. Emit the handoff summary
Close with a short summary for the next session:
- Shipped: PRs merged, sprints closed (with scores)
- Open: current sprint state, pending gates, unmerged branches
- Next: the single most useful thing the next session should pick up
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 · 37 lines · 0 tokens per session scan A 04206e41e0bd
wrap-session is a command published in the GitHub repository srbryers/slope (6 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 408 tokens. 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 commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…