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 ShipBook/shipbook-mcp --skill list-issuesgit 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/list-issues)<a href="https://agentmods.dev/skills/shipbook/shipbook-mcp/list-issues"><img src="https://agentmods.dev/badge/skills/shipbook/shipbook-mcp/list-issues.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.00043 | $0.00519 |
| Opus 5 | $0.00022 | $0.00260 |
| Sonnet 5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
list-issues 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 6d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Issues
Use Shipbook MCP tools to list and analyze classified errors and warnings in an application. Defaults to errors — set severity to Warning for warnings.
Steps
- Call
get-account-appsto list available apps (returns name, appId, platform, key, integration). If the user didn't specify an app, detect the current project's platform from the codebase and filter matching apps. If there are still multiple matches, ask the user which one. - Call
get-loglytics-errorswith the appId to retrieve grouped error categories. - Analyze the errors and group them by root cause — multiple error entries may stem from the same underlying issue (e.g., a network failure causing errors in different parts of the code, or one null value propagating through several functions). Present grouped by reason, not just as a flat list.
- Present error groups ranked by impact (total occurrence count, affected devices/sessions across all errors in the group).
- For the most critical error group (or the one the user asks about), use the
keyof each error in the group withget-logsto find specific instances. - Error logs include
fileNameandlineNumber— use these to locate the exact code in the project and analyze it. Reading the actual code is often the best way to understand why the error happens. - To get context around a specific error, call
get-logsagain with the samesessionID, setmaxOrderIdto the error's orderId + 10, and remove the severity filter. This shows what happened leading up to the error. - Summarize findings: what the root cause is, how often it occurs, which users/devices are affected, and suggest code fixes based on the code analysis and log context.
Output
- First present each error individually ranked by impact (occurrence count, affected devices/sessions)
- Then group them by root cause — show which errors stem from the same underlying issue and explain why
- For investigated errors, show the chain of events leading to the crash/error
- Suggest concrete fixes when the root cause is visible in the logs
- If the user's codebase is open, offer to locate and fix the relevant code
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.
- 6d ago First seen · 28 lines · 43 tokens per session scan A 441c90f0ff93
list-issues is a skill published in the GitHub repository ShipBook/shipbook-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 519 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.