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 taosdata/agent-skills --skill idmp-workflow-alert-debuggit clone --depth 1 https://github.com/taosdata/agent-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/taosdata/agent-skills/idmp-workflow-alert-debug)<a href="https://agentmods.dev/skills/taosdata/agent-skills/idmp-workflow-alert-debug"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-workflow-alert-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.00038 | $0.00740 |
| Opus 5 | $0.00019 | $0.00370 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
idmp-workflow-alert-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 7d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workflow: alert debug
Read ../idmp-shared/SKILL.md first.
Recommended references
Missing context to resolve first
- Failure boundary.
- Reread window.
- Event scope.
- Notify-rule scope.
- Whether the complaint is “no event opened” or “event opened but delivery failed”.
Constrained live behaviors
confirmandresendhave side effects.status=Unackis the safest default when the operator needs an open event.- Prefer
analysisIdwhen correlating an event back to alert creation. - Notification history can lag behind resend.
- A linked analysis was already deleted in some valid debug branches.
- Capture event evidence before any acknowledge or resend action.
Execution flow
- Start with
idmp-cli event count listandidmp-cli event events list --paramsto decide whether the failure is missing events or missing delivery. - Use
idmp-cli event events get --paramsandidmp-cli event events items --paramsto lock a single event and its payload. - Only after evidence is captured should you consider
idmp-cli event events confirm --ack-risk --paramsoridmp-cli event events resend --ack-risk --params. - Read
idmp-cli notification config listto confirm the notification side is configured. - Finish with
idmp-cli notification page list --paramsto inspect delivery history after the event-side review.
Exception paths
- If no event exists, stop and hand off to alert creation or analysis diagnosis.
- If delivery history is empty right after resend, call out history lag before declaring failure.
- Any temporary debug artifact must be deleted before you leave the workflow.
Validation scenarios
1. Event exists and explains the alert
Use idmp-cli event events list --params, then idmp-cli event events get --params. The result should prove the alert opened and what the event currently says.
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.
- 7d ago First seen · 70 lines · 38 tokens per session scan A 030b6b6b1d9a
idmp-workflow-alert-debug is a skill published in the GitHub repository taosdata/agent-skills (3 stars, last pushed 23d ago), licensed MIT. It adds 38 tokens to every session and 740 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-30.
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.