Borrowing it
Nothing to install: this file belongs to sevenschulte/agentic-harness. 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/sevenschulte/agentic-harness/main/.claude/skills/wrap-up/SKILL.mdgit clone --depth 1 https://github.com/sevenschulte/agentic-harnessWrote 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/sevenschulte/agentic-harness/wrap-up)<a href="https://agentmods.dev/skills/sevenschulte/agentic-harness/wrap-up"><img src="https://agentmods.dev/badge/skills/sevenschulte/agentic-harness/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/skills/sevenschulte/agentic-harness/wrap-up"><img src="https://agentmods.dev/badge/skills/sevenschulte/agentic-harness/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.00057 | $0.00979 |
| Opus 5.5 | $0.00023 | $0.00392 |
| Sonnet 5.5 | $0.00011 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
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 2mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap Up
You are closing a work session. Your job is to update memory/ACTIVE.md so the
next session has everything it needs to continue: where we were, what got done,
what's still in flight, what's next.
Without this step, ACTIVE.md stagnates and the next session starts cold even
though the codebase hasn't.
When to wrap up
- User says "wrap up" / "let's stop" / "end session" / "that's it for today"
- About to stop responding after meaningful work (a deliverable shipped, a decision made, an investigation concluded, a PR opened)
- Switching to a completely different topic or project
Skip for purely conversational sessions with no deliverables.
Step 1 — Read the current ACTIVE.md
You are updating, not rewriting.
memory/ACTIVE.md
Expected shape (create if missing):
# Active Work
## Current Focus
<what we're working on right now>
## In Progress
- [ ] <task with a checkbox>
- [x] <completed task>
## Next Up
- <upcoming task>
## Parking Lot
- <idea to revisit>
## Completed
- **<title>** (<date>) — <one line>. Details: <pointer to memory/projects/...>
## Session Notes
*<date>:* <one-paragraph session summary>
Step 2 — Analyse this session
Identify:
- Focus — what was the main thing we worked on?
- Done — what got finished? (mark
[x]) - In flight — what's started but not finished? (
[ ]) - Next — what's the immediate next step for whoever continues?
- Blockers — what's waiting on something external?
- Discovered — new tasks that came up but aren't urgent? (parking lot)
Step 3 — Update ACTIVE.md
- Current Focus: rewrite to reflect today's work, including status if relevant (blocked, in review, waiting on X)
- In Progress: mark completed items
[x], add any new in-flight items - Next Up: move items in/out as priorities shift
- Parking Lot: append anything worth remembering later
- Completed: one-line index entry pointing at the fuller write-up elsewhere.
Don't inline long descriptions; details live in
memory/projects/<...>ormemory/research/<...> - Session Notes: prepend one short paragraph (date in YYYY-MM-DD, one paragraph summarising what happened and why)
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.
- 2mo ago First seen · 132 lines · 57 tokens per session scan A 2e07ea72c387
wrap-up is a skill published in the GitHub repository sevenschulte/agentic-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 979 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-08-31.
Other skills, from other repositories
lean-ctx
Use LeanCTX Context Gateway tools to select task-relevant code context, apply supported controls, reuse local knowledge and inspect recorded evidence. Use when lean-ctx MCP tools (ctx) are available or file, search or command output needs a focused view.
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…
memex-sync
Sync Zettelkasten cards across devices via git.
template-publish
Publishing scripts for DOI-bearing project releases, optional mirror uploads, PyPI release validation, post-publish verification, and publication export. Use with docs/guides/publication-runbook.md for standalone GitHub + Zenodo release workflows.
automotive-engineering-technician
Use when a task needs the judgment of an Automotive Engineering Technician — setting up and instrumenting test equipment (strain-gauge bridges, thermocouples, load/torque sensors) to an engineer's written test plan, selecting DAQ sample rate and an SAE J211 CFC filter class for a vehicle test channel, verifying…
aviation-inspector
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs.…