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/sssstwee/tastedistill/tasted-debugnpx skills add sssstwee/tastedistill --skill tasted-debuggit clone --depth 1 https://github.com/sssstwee/tastedistillWrote 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/sssstwee/tastedistill/tasted-debug)<a href="https://agentmods.dev/skills/sssstwee/tastedistill/tasted-debug"><img src="https://agentmods.dev/badge/skills/sssstwee/tastedistill/tasted-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 | $0.00062 | $0.00593 |
| Opus 5 | $0.00031 | $0.00296 |
| Sonnet 5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
tasted-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 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.
This is a copy
91% identical to debug — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug: Prove The Cause
Use this skill when the task starts from a symptom.
Prefix your first response line with ⚗️ inline, not as its own paragraph.
Before the workflow, apply ../../shared-rules/personalization.md for explicit TasteD/TasteDistill invocations.
Apply ../../shared-rules/runtime-hygiene.md when debugging uses helper scripts, browser checks, local servers, screenshots, traces, or other generated artifacts.
Outcome Contract
- Outcome: proven root cause, minimal fix or handoff, and verification evidence.
- Done when: every observed symptom fits the explanation and the fix is checked by a reproducible test or runtime observation.
- Evidence: repro steps, logs, traces, state, source paths, generated artifacts, tests, screenshots, and command output.
Workflow
- List the observed symptoms.
- Reproduce the issue or define the missing evidence.
- Trace from symptom to source.
- State a one-sentence root-cause hypothesis with evidence.
- Make the smallest fix that addresses the cause.
- Run the narrow regression check.
- Search for the same bug shape if the root cause is reusable.
Coding Guardrails
For fixes, apply ../../shared-rules/coding-guardrails.md:
- Think before coding: do not edit until the root-cause hypothesis is specific and evidence-backed.
- Simplicity first: fix the cause directly; avoid broad rewrites, new abstractions, or speculative compatibility.
- Surgical changes: keep the patch to the failure path; search siblings only for the same bug shape.
- Goal-driven execution: prove the original symptom changed with a reproducible check.
CodeGraph
For root-cause analysis in a Git repository, ../../shared-rules/personalization.md should already have ensured the local CodeGraph index. When codegraph_* tools are available, prefer codegraph_trace for "how does X reach Y", codegraph_callers / codegraph_callees for one-hop flow, and codegraph_context for nearby implementation context. Read target files directly before editing.
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.
- 5d ago First seen · 61 lines · 62 tokens per session scan A 76a3a5b76e5a
tasted-debug is a skill published in the GitHub repository sssstwee/tastedistill (2 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 593 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to debug, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
ix
This skill should be used when answering structural questions about a codebase: understanding what a symbol is, tracing flows, measuring change impact, finding callers/callees/imports, or detecting code smells. It drives the Ix CLI (ix map/explain/trace/impact/search/rank/smells) against a persistent code graph stored…
memory-audit-pattern-extraction
模式提取与失效解药分析。当发现多条记忆在讲同一个教训，或发现自己在一而再再而三地犯同样的错误时使用。.
services-audit-cron
Use when scheduling the canonical biweekly services-audit cron loop for Empirica's AI service scanner (Phase 3). The auditor body is empirica services-audit — captures a fresh scan, diffs against the previous, and emits a notification when novel running services appear. This skill provides the prompt template that…