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-datasource-diagnosegit 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-datasource-diagnose)<a href="https://agentmods.dev/skills/taosdata/agent-skills/idmp-workflow-datasource-diagnose"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-workflow-datasource-diagnose/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/taosdata/agent-skills/idmp-workflow-datasource-diagnose"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-workflow-datasource-diagnose.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.00042 | $0.00826 |
| Opus 5 | $0.00021 | $0.00413 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
idmp-workflow-datasource-diagnose 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 10d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workflow: datasource diagnose
Read ../idmp-shared/SKILL.md first.
Recommended references
Missing context to resolve first
- Credential source.
- Verification rereads.
- The target connection, database, or table that the operator thinks is broken.
- Whether the complaint is reachability, metadata visibility, or model mismatch.
- Which element or template mapping should be compared back to source metadata.
Constrained live behaviors
- Do not copy
connections getintoconnectivity create. datasource check listfor the built-in TDengine listener.- After any write-like probe or import, reread.
- Read the connection object before probing reachability.
- Additional properties and metadata are evidence; they do not replace a live connectivity probe.
- Metadata diagnosis stays ordered: connection -> probe -> db -> table -> column -> model mapping.
Execution flow
- Read
idmp-cli datasource connections listandidmp-cli datasource connections get --paramsbefore any probe. - Use
idmp-cli datasource additional-properties list-get --paramsto capture datasource-side context. - Reread
idmp-cli datasource check listand then runidmp-cli datasource connectivity create --ack-risk --datato separate summary health from live reachability. - Use
idmp-cli datasource dbnames list --params,idmp-cli datasource tablenames list --params, andidmp-cli datasource columninfo create --ack-risk --paramsto lock the metadata boundary. - Compare that metadata with
idmp-cli attr-template elements attributes --params, and useidmp-cli datasource csv create --ack-risk --paramsonly when the diagnosis includes a write-like CSV probe. - Reread
idmp-cli data records listif the diagnosis also touches import or export traces.
Exception paths
- If the connectivity probe fails, fall back to
datasource check listplus metadata reads before interpreting missing tables as schema bugs. - If metadata exists but the model does not match, report the exact column or mapping mismatch.
- If record traces are absent, say whether the gap is ingestion history or datasource visibility. Capture whether the root cause is connectivity.
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.
- 10d ago First seen · 71 lines · 42 tokens per session scan A 21019d2113c0
idmp-workflow-datasource-diagnose is a skill published in the GitHub repository taosdata/agent-skills (3 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 826 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
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.
django-perf-review
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.