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 midFang/ai-agent-skills-workflow --skill debug-tag-addgit clone --depth 1 https://github.com/midFang/ai-agent-skills-workflowWrote 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/midfang/ai-agent-skills-workflow/debug-tag-add)<a href="https://agentmods.dev/skills/midfang/ai-agent-skills-workflow/debug-tag-add"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/debug-tag-add/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/midfang/ai-agent-skills-workflow/debug-tag-add"><img src="https://agentmods.dev/badge/skills/midfang/ai-agent-skills-workflow/debug-tag-add.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.00556 |
| Opus 5 | $0.00039 | $0.00278 |
| Sonnet 5 | $0.00016 | $0.00111 |
| Haiku 4.5 | $0.00008 | $0.00056 |
Grade A, and why
debug-tag-add 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Tag Add
Use this skill to add temporary diagnostic logs for one specific issue. The goal is to make user-provided logs enough to locate the missed branch or wrong state, while keeping the change easy to remove later.
Workflow
- Identify the exact bug scenario, expected behavior, actual behavior, and the state machine or entry points involved.
- Choose one fixed tag for the whole investigation. Prefer a short issue-specific tag such as
CastCloseDebug; if the user provides a tag, use it exactly. - Add logs only at decision boundaries that can explain the bug:
- state/event received
- target/session matching result
- key flags used by branching logic
- error code/message/description
- final branch/action chosen
- Keep logs temporary and searchable. Use the same tag string in every added log line.
- Avoid logging secrets, tokens, cookies, request bodies with personal data, full URLs with credentials, or large binary/text payloads.
- Prefer existing project logging helpers and style. Do not introduce a new logging framework.
- Run a search for the tag before finishing so the user knows exactly what to filter in Logcat or other logs.
Log Shape
Each log should answer: "where am I, which object/session is this, what condition values matter, and what branch will happen?"
Good examples:
logD(
"CastCloseDebug",
"start bridge state: type=${state::class.simpleName}, " +
"matchesCurrentTarget=$matchesCurrentTarget, belongsToCurrentTarget=$belongsToCurrentTarget, " +
"errorCode=${state.error?.errorCode}, showDialog=${state.showDialog}",
)
logD(
"CastCloseDebug",
"global disconnected: deviceId=${deviceId.orEmpty()}, " +
"wasConnected=$wasConnected, hadEstablishedSession=$hadEstablishedSession, " +
"willShowDeviceClosed=$shouldShowDeviceClosedDialog",
)
Finish Criteria
- Tell the user the fixed tag to filter.
- Mention the main files or code paths instrumented.
- Make clear the logs are temporary and should be removed after the issue is confirmed fixed.
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 · 56 lines · 79 tokens per session scan A 2ca1d77700fd
debug-tag-add is a skill published in the GitHub repository midFang/ai-agent-skills-workflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 556 once invoked, about $0.0004 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.