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 cabaynes/charles-claude-skills --skill putdowngit clone --depth 1 https://github.com/cabaynes/charles-claude-skillsWrote 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/cabaynes/charles-claude-skills/putdown)<a href="https://agentmods.dev/skills/cabaynes/charles-claude-skills/putdown"><img src="https://agentmods.dev/badge/skills/cabaynes/charles-claude-skills/putdown/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/cabaynes/charles-claude-skills/putdown"><img src="https://agentmods.dev/badge/skills/cabaynes/charles-claude-skills/putdown.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.00098 | $0.02817 |
| Opus 5.5 | $0.00039 | $0.01127 |
| Sonnet 5.5 | $0.00020 | $0.00563 |
| Haiku 4.5 | $0.00010 | $0.00282 |
Grade A, and why
putdown 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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/putdown — Context handoff before clearing
The user is about to clear the context window and start fresh. Your job: capture everything a new agent would need so the next session loses no momentum.
Renamed from
/checkpointon 2026-06-12 (paired with/resume→/pickup) because those names shadow Claude Code built-ins (/checkpointaliases/rewind;/resumeopens the conversation picker). On 2026-06-13 the handoff files also moved from.checkpoints/→.putdowns/to drop the old term entirely. If you ever see a stray.checkpoints/folder, it predates the move — treat it as a putdown.
Step 0 — Announce what's about to run
If /takenotes is installed, a putdown is two operations, not one. Print this first so the user knows what's running and in what order:
/putdown runs two skills, in this order:
1. /takenotes — harvest this session into memory, CLAUDE.md, and docs/
2. /putdown — write the handoff file, then commit and push everything
If /takenotes is not installed, skip the announcement. Either way this is an announcement, not a prompt — don't wait for confirmation, continue to Step 1.
Step 1 — Read current state (parallel)
Before writing anything, gather context. Run these in parallel:
pwd— where the session is rootedgit statusandgit log --oneline -10— if it's a git repo (skip silently if not)git diff --stat— what's changed, uncommitted- Read the project-level
CLAUDE.mdif one exists in the CWD - Read
~/.claude/projects/<project-slug>/memory/MEMORY.mdto know which memory files exist - Check the current TodoWrite list state (if you have one in this session — recall from conversation, don't invent)
echo "$CLAUDE_CODE_ENTRYPOINT"— which surface this is.cli= terminal (standalone or VSCode's integrated terminal); anything else (or empty) = VSCode's visual-editor chat panel or another GUI surface. This decides the clear-context instructions in Step 5.
Also pull from your conversation memory:
- What was the user actually trying to accomplish in this session?
- What did you finish? What's half-done?
- What file paths and line numbers are you in the middle of?
- What did you try that didn't work, and why?
- Any decisions made with non-obvious rationale?
- Any errors, blockers, or open questions waiting on the user?
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.
- 1mo ago Changed 882ae6ac164a
- 1mo ago First seen · 161 lines · 98 tokens per session scan A 0e5b319b1ab0
putdown is a skill published in the GitHub repository cabaynes/charles-claude-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 2,817 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-08-31.
Other skills, from other repositories
dream
A read-only review of project memories, notes, instructions, documents, and selected session records that produces a detailed report and a browser-viewable HTML report. It suggests ideas and insights but does not apply changes.
wake
A workflow for applying only the changes a user selected from a previously created dream report. It reads the saved choices and updates the specified memory or project notes.
metabot
Unified MetaBot CLI for personal Memory, Skill Hub, durable Agent Bus messaging, agent registry, Agent Teams, T5T, scheduling, and bridge runtime operations.
context-budget
Use when a coding session is burning context fast, output is drowning in noise, the model keeps forgetting earlier decisions, or the user asks to reduce tokens, stop the verbose narration, work in a huge repo, or make a long session survive. Covers what to read, what to summarize, what to write to disk, and when to…
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…
conversation-archaeologist
Mine ALL past Claude conversations to build a living 'User Manual About You'. Extract writing style, business context, goals, preferences, and patterns. Make all other skills smarter with context.