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 mshadmanrahman/claude-for-designers --skill wrap-upgit clone --depth 1 https://github.com/mshadmanrahman/claude-for-designersWrote 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/mshadmanrahman/claude-for-designers/wrap-up)<a href="https://agentmods.dev/skills/mshadmanrahman/claude-for-designers/wrap-up"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/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/mshadmanrahman/claude-for-designers/wrap-up"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/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.00104 | $0.00880 |
| Opus 5.5 | $0.00042 | $0.00352 |
| Sonnet 5.5 | $0.00021 | $0.00176 |
| Haiku 4.5 | $0.00010 | $0.00088 |
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 16d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The student typed /wrap-up. They are done for the day and about to close this chat. Your job is to save what happened in this session so that tomorrow, in a fresh chat, /pick-up can carry on from exactly here.
A new chat remembers nothing from this one. The log is the only thing that carries over, so the four lines you write are all tomorrow's Claude will know.
Step 1. Work out where the entry goes
The log lives beside the work it describes. Never in one shared file at root.
- Client work goes to
projects/<client>/log.md. The client is the folder the session worked in:edubridge, or their own client folder. - Career work (Classes 7 and 8, anything in
career-vault/) goes tocareer-vault/log.md. - Work on
principles/claude-contract.md(Class 2) goes to the log of their project, because Class 2 also writes the project contract and that is where they will look for it. - Never write to
projects/_new-client/log.md. That folder is an empty template.
If the session touched two projects, write one entry into each project's log, each holding only what happened in that project. One client's notes never land in another client's file.
If log.md does not exist yet, create it with the header shown in Step 3.
Step 2. Propose, then let them correct
Do not write straight away. Draft the entry from the session and show it:
Before I save, check this:
Did: ran /grill-me on the brief, finished brief-v3-interrogated.md
Decided: bKash is its own flow, because the parent leaves the site
Open: the client has not said who handles refunds
Next: write scope-email.md
Anything wrong or missing?
The Decided line matters most. Write the decision and the reason, in their words where you can. If you are not sure something was a decision, ask rather than guess: the decisions are theirs, and a wrong one saved here gets repeated tomorrow as if it were settled.
If nothing was decided, write "nothing decided". Never invent one.
When they answer, apply their corrections. If they say it is fine, save it.
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.
- 16d ago First seen · 80 lines · 104 tokens per session scan A 1547e3fad41e
wrap-up is a skill published in the GitHub repository mshadmanrahman/claude-for-designers (39 stars, last pushed 16d ago), licensed MIT. It adds 104 tokens to every session and 880 once invoked, about $0.0004 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-09-30.
Other skills, from other repositories
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
process-flowchart-designer
Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.