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 skills/shipbook/shipbook-mcp/debug-sessionnpx skills add ShipBook/shipbook-mcp --skill debug-sessiongit clone --depth 1 https://github.com/ShipBook/shipbook-mcpWrote 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/shipbook/shipbook-mcp/debug-session)<a href="https://agentmods.dev/skills/shipbook/shipbook-mcp/debug-session"><img src="https://agentmods.dev/badge/skills/shipbook/shipbook-mcp/debug-session.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 | $0.00037 | $0.00349 |
| Opus 5 | $0.00018 | $0.00175 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
debug-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 4d 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
Debug User Session
Use Shipbook MCP tools to debug what happened in a specific user's session.
Steps
- Call
get-account-appsto identify the app (returns name, appId, platform, key, integration). If the user didn't specify an app, detect the current project's platform and filter matching apps. If there are still multiple matches, ask the user which one. - Call
get-logsfiltered by the user identifier provided (email, userId, userName, udid) with severity=Error to find problems. - If errors are found, take the
sessionID from the error log and callget-logsagain withmaxOrderIdset to the error's orderId + 10 and without severity filter — this shows the context leading up to the error. - Every log includes
fileNameandlineNumber— use these to locate and read the actual code in the project to understand what happened. - If no errors are found, broaden the search (remove severity filter, adjust time range) to find the user's activity.
- Use
minOrderId/maxOrderIdto navigate through long sessions.
Output
- Reconstruct the user's session timeline chronologically
- Highlight any errors or warnings encountered, with their fileName and lineNumber
- Identify the sequence of events leading to any issues
- Suggest fixes based on both the log context and the actual code at the error location
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.
- 4d ago First seen · 25 lines · 37 tokens per session scan A c7219fe94360
debug-session is a skill published in the GitHub repository ShipBook/shipbook-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 349 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…