odyssey: Agent for Claude Code

.claude/agents/wrap-up.md

wrap-up is an agent for Claude Code from KhourySpecialProjects/odyssey. It costs 50 tokens per session (1,496 once invoked), scanned A, original, MIT.

An end-of-session review agent that records progress, captures lessons, and checks whether work remains incomplete. It updates project guidance and writes a progress file for the next session.

In plain words
What is it for?
It helps summarize recent commits and changes, record completed and blocked work, document decisions, and update agent instructions based on what happened.
Why use it?
Important decisions, unfinished tasks, and recurring sources of friction are easy to lose when a coding session ends. A wrap-up creates a written handoff and highlights what needs attention next.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is KhourySpecialProjects/odyssey's own configuration. It tells Claude Code how to work on odyssey itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything odyssey configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/KhourySpecialProjects/odyssey/production/.claude/agents/wrap-up.md
Clone the repo
git clone --depth 1 https://github.com/KhourySpecialProjects/odyssey

Made for: Claude Code.

Wrote 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.

agentmods badge for wrap-up

README.md
[![agentmods](https://agentmods.dev/badge/agents/khouryspecialprojects/odyssey/wrap-up/github.svg)](https://agentmods.dev/agents/khouryspecialprojects/odyssey/wrap-up)
Your own site
<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.

agentmods 80×15 button for wrap-up

Your own site · 80×15
<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>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,496 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured today against content hash 5f5f4cead88f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-03, from the pricing page.

Security

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.

.claude/agents/wrap-up.md · 203 lines

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

  1. 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
  2. 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

Phase 2: Remember It

Review what was learned during the session. Write learnings to the dedicated learnings folder — NOT directly into reference docs.

Read the full file on GitHub · 203 lines

Changes

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.

  1. today First seen · 203 lines · 50 tokens per session scan A 5f5f4cead88f

Subscribe to this mod's changes

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.

Related

Other agents, from other repositories