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 AdvayRoy/slate-skills --skill slate-debuggit clone --depth 1 https://github.com/AdvayRoy/slate-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/advayroy/slate-skills/slate-debug)<a href="https://agentmods.dev/skills/advayroy/slate-skills/slate-debug"><img src="https://agentmods.dev/badge/skills/advayroy/slate-skills/slate-debug.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.00028 | $0.00255 |
| Opus 5 | $0.00014 | $0.00128 |
| Sonnet 5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
slate-debug 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 8d 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
slate-debug
Debug in minimum useful tokens.
Mission
Find root cause, patch minimal fix, prove result.
Workflow
- Read exact error.
- Extract shortest decisive error line.
- Inspect relevant file/function only.
- State one primary hypothesis.
- Patch smallest fix.
- Rerun failing command first.
- Report proof or remaining unknown.
Output
Error:
Cause:
Fix:
Proof:
Unverified:
Rules
- No shotgun changes.
- No unrelated refactors.
- No suppressing errors to pass tests.
- No full log dumps unless asked.
- If cause is uncertain, say
Likely cause:notCause:. - If no test was run,
Proof:must not claim success.
Example
Error: `TypeError: user.email is undefined`
Cause: `.find()` can return null.
Fix: guard `user` before `.email`.
Proof: `npm test auth.middleware.test.ts` passed.
Unverified: full suite not run.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 55 lines · 28 tokens per session scan A 35a666b4f542
slate-debug is a skill published in the GitHub repository AdvayRoy/slate-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 255 once invoked, about $0.0001 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.