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 FarzamMohammadi/the-engineer --skill wrap-sessiongit clone --depth 1 https://github.com/FarzamMohammadi/the-engineerWrote 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/farzammohammadi/the-engineer/wrap-session)<a href="https://agentmods.dev/skills/farzammohammadi/the-engineer/wrap-session"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/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/skills/farzammohammadi/the-engineer/wrap-session"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/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.00037 | $0.00557 |
| Opus 5 | $0.00018 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap Session
End the current session cleanly so the next one picks up without losing a beat.
Step 1: Update docs/archived/implementation-docs/9-oss-ready/active.md
Read docs/archived/implementation-docs/9-oss-ready/active.md, then update the Status section to reflect:
- What was just completed this session
- What we're doing next session
- Current state of the overall work
Keep the rest of active.md intact (Current Focus, What We're Doing, Deliverables). Only the Status section changes.
Step 2: Log the Session
- Check
docs/archived/implementation-docs/9-oss-ready/sessions/for the latest session number - Create the next sequential file (e.g.,
002.md,003.md)
Format:
# Session [NNN] — [YYYY-MM-DD]
## What Happened
[2-4 sentences summarizing the session. Be succinct.]
## Decisions Made
[Numbered list of decisions, or "None" if purely execution work.]
## What's Next
[What the next session should start with.]
Step 3: Commit
Run /commit to stage and commit all changes from this session.
Step 4: Starter Prompt
Generate a starter prompt for the next session. This is a self-contained message the user can paste into a fresh chat to pick up exactly where this session ended.
The prompt should:
- Tell the agent which files to read first (always start with
docs/archived/implementation-docs/9-oss-ready/active.md, then the latest session log) - Include any phase-specific files relevant to the current work (read active.md to determine these)
- State the project context in one sentence
- State the working mode based on what we're actually doing (read active.md — it may be code, testing, design, review, etc.). Always include: collaborate deeply, use Q&A tool, never assume, never rush.
- Say to pick up where the last session left off
Present it in a code block, ready to copy-paste.
Output
Present to the user:
- Summary of what was logged
- List of files updated/created
- The starter prompt in a code block
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 · 77 lines · 37 tokens per session scan A 24be11d4fd18
wrap-session is a skill published in the GitHub repository FarzamMohammadi/the-engineer (12 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 557 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-30.
Other skills, from other repositories
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
akigitcommit
Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.