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 agentmods add commands/adamwstauffer/shidler/breakpointgit clone --depth 1 https://github.com/adamwstauffer/shidlerWrote 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/commands/adamwstauffer/shidler/breakpoint)<a href="https://agentmods.dev/commands/adamwstauffer/shidler/breakpoint"><img src="https://agentmods.dev/badge/commands/adamwstauffer/shidler/breakpoint.svg" alt="Measured on agentmods" 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.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
breakpoint 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 5d 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.
What it actually says
/breakpoint — Emit a session pickup prompt
Run at a context break — before /compact or /clear, when a grading pass is mid-flight, at the end of a phase, or before a risky git mv restructure — to capture everything a fresh session needs to resume.
What this command does
You produce one structured pickup prompt and emit it to the conversation so it survives compaction. You do not change git state. You speak directly — this is a status artifact, not a narrative.
Follow the methodology in .claude/skills/breakpoint/SKILL.md end-to-end: gather the inputs in the order specified (branch/worktree state, unpushed commits, open + merged PRs, task list, in-flight decision memos, active grading passes, standing constraints), render the pickup-prompt block exactly, and respect every edge case (unpushed commits lead, stacked PRs rendered bottom-up, concurrent-session caveats flagged, score numbers never included, read-only).
Argument
[<note>] — Optional one-line hint about what you're working on, used in the prompt header. If omitted, infer it from the session.
Output
- The full
## 🔖 Pickup Promptblock (to the conversation). - The same block persisted to
docs/breakpoints/<YYYY-MM-DD-HHMM>-<slug>.md(gitignored working state), superseded breakpoints archived in the same pass. - One terminal line:
Breakpoint captured + persisted to <path> — <N> open PRs, <N> unpushed commits, resume at: <entry point>. Run /compact next.
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.
- 5d ago First seen · 20 lines · 0 tokens per session scan A 788ee80b4e24
breakpoint is a command published in the GitHub repository adamwstauffer/shidler (10 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 tokens. 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.