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/taosdata/agent-skills/idmp-datasourcenpx skills add taosdata/agent-skills --skill idmp-datasourcegit 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-datasource)<a href="https://agentmods.dev/skills/taosdata/agent-skills/idmp-datasource"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-datasource.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.00041 | $0.00959 |
| Opus 5 | $0.00020 | $0.00479 |
| Sonnet 5 | $0.00008 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
idmp-datasource 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
datasource
Read ../idmp-shared/SKILL.md first.
What this skill covers
- Inspect datasource connections, redacted connection details, connectivity probes, database and table discovery, and column metadata.
- Keep read-first metadata diagnosis separate from mutating import workflows.
Recommended reference
Missing context to resolve first
- Credential source.
- Verification rereads.
- Which datasource connection or environment is in scope.
- Which database, table, or stable must be traced.
- Whether the operator wants metadata only or a full model-to-source mapping explanation.
Constrained live behaviors
datasource connections getcan return redacted secrets.datasource check listis the safe health probe.datasource columninfo createis a write-like metadata probe.- Connection reads can be redacted and still be usable for diagnosis.
- Connectivity probes validate reachability, not schema correctness.
- Metadata walks should stay ordered: connection -> connectivity -> databases -> tables -> columns.
- Source-to-model explanations must use the real mapped fields, not guessed TDengine column names.
Execution flow
- Start with
idmp-cli datasource connections list, then lock the exact connection throughconnections get. - Run
idmp-cli datasource check listbefore deeper diagnosis so connection-health boundaries are explicit. - Use
idmp-cli datasource connectivity create --ack-risk --dataonly after the target connection is fixed; treat it as live reachability proof, not schema proof. - Walk
dbnames -> tablenames -> columninfoin order so every metadata claim stays grounded in the same database and table scope. - Finish by comparing the discovered source fields against the real model mapping rather than guessed TDengine column names.
Evidence of completion
- A connection diagnosis is only complete when the connection reread and the health probe refer to the same connection ID.
- A metadata claim is only complete when the same database and table survive the
dbnames -> tablenames -> columninfochain. - Redacted connection reads are still valid evidence; never treat masked secrets as missing data.
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.
- 6d ago First seen · 91 lines · 41 tokens per session scan A 8a2ee8303505
idmp-datasource is a skill published in the GitHub repository taosdata/agent-skills (3 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 959 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
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…