Borrowing it
Nothing to install: this file belongs to KhourySpecialProjects/odyssey. 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/KhourySpecialProjects/odyssey/production/.claude/agents/wrap-up.mdgit clone --depth 1 https://github.com/KhourySpecialProjects/odysseyWrote 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/agents/khouryspecialprojects/odyssey/wrap-up)<a href="https://agentmods.dev/agents/khouryspecialprojects/odyssey/wrap-up"><img src="https://agentmods.dev/badge/agents/khouryspecialprojects/odyssey/wrap-up/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/agents/khouryspecialprojects/odyssey/wrap-up"><img src="https://agentmods.dev/badge/agents/khouryspecialprojects/odyssey/wrap-up.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.00050 | $0.01496 |
| Opus 5.5 | $0.00020 | $0.00598 |
| Sonnet 5.5 | $0.00010 | $0.00299 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
wrap-up 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 today.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running end-of-session wrap-up for the Odyssey education platform. Run four phases in order. Auto-apply changes without asking for approval on each one. Present a consolidated report at the end.
Phase 0: Gather Session Context
Before doing anything, understand what happened this session:
git log --oneline -15
git diff --stat
git branch --show-current
Check for recent plan files in docs/plans/ (if the directory exists). This gives you the branch name, what was worked on, and how much changed — essential context for writing meaningful learnings.
Phase 0.5: Write Progress File
Write a progress file so the next session can pick up where this one left off.
Save to docs/plans/PROGRESS.md (overwrite if exists):
# Session Progress
**Date:** YYYY-MM-DD
**Branch:** [current branch]
**Focus:** [what was worked on this session — 1 sentence]
## Completed This Session
- [List of completed tasks/changes]
## In Progress
- [Anything started but not finished, with file paths]
## Blocked / Needs Attention
- [Anything that needs human input or investigation]
## Key Decisions Made
- [Design decisions, trade-offs, or assumptions made this session]
## Next Steps
- [Ordered list of what should happen next]
- [Reference specific plan files if applicable]
If no meaningful work was done (e.g., just exploration or questions), skip this phase.
Phase 1: Check Completeness
-
Check for any remaining quality issues:
- Run:
cd frontend && npx prettier --check app components lib && npx eslint app components --ext .js,.ts,.tsx && npm test - Report any remaining issues
- Run:
-
Check for orphaned work:
- Are there plan files in
docs/plans/with tasks not marked done? - Are there TODO comments added during this session?
- Are there files created in wrong locations per project conventions?
- Flag anything that needs attention next session
- Are there plan files in
Phase 2: Remember It
Review what was learned during the session. Write learnings to the dedicated learnings folder — NOT directly into reference docs.
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.
- today First seen · 203 lines · 50 tokens per session scan A 5f5f4cead88f
wrap-up is an agent published in the GitHub repository KhourySpecialProjects/odyssey (7 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,496 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-10-02.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…