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-panelgit 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-panel)<a href="https://agentmods.dev/skills/taosdata/agent-skills/idmp-panel"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-panel/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-panel"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-panel.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.00029 | $0.01974 |
| Opus 5 | $0.00015 | $0.00987 |
| Sonnet 5 | $0.00006 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
idmp-panel 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 9d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
panel
Read ../idmp-shared/SKILL.md first.
Before any write: Follow the 🛑 Destructive op confirmation protocol. Read-only commands stay read-only here, but delete / write / patch flows still require the shared yes-gate.
Recommended shortcuts
| Shortcut | Purpose |
|---|---|
+list |
List panels under one element. |
+search |
Search panels globally. |
+templates |
List panel templates available to one element. |
Recommended references
Missing context to resolve first
| Context | Why it must be resolved before create or verify |
|---|---|
| Owner element | You need the final elementId for list, get, naming, create, and every verification call. |
| Candidate panel name | panel.panels.new-name requires both elementId and a proposed name. |
| Verification mode | Decide whether this panel should generate SQL at all, and whether you need plain query and sqls checks or advanced-query verification. |
| Dashboard placement target | Decide whether the panel remains standalone or must be inserted into a dashboard before the workflow counts as complete. |
| Refresh owner | Decide whether refresh belongs on the panel shell or the dashboard shell so refreshInterval lands in the right params block. |
Constrained live behaviors
- Prefer
POST /api/v1/ai/panels/createfor natural-language panel requests, then persist the returned draft throughpanel.panels.create. Use the structured panel DTO workflow only as fallback when the draft is unsuitable or persistence fails. panel.panels.new-namerequires a candidatename; do not call it with only the owner scope.- Text and manual panels can legitimately return
generated SQL is empty, soqueryis inapplicable for those panel types. panel verify createvalidates only the time-range payload withfromandto; use plain--data, not--params, and do not sendelementId.panel.panels.queryandpanel.panels.createuse the panel DTO shape.panel.panels.sqlsuses the same DTO together with owner--params.panel verify create-postis only for advanced-query payloads. Keepuuid,advancedQueryType,querySqls, and the advanced query fields inside that single DTO.- If a child-scope no-code DTO collapses to self scope on reread or returns empty-body
400, capture the working SQL and switch to the advanced fallback instead of treating the first attempt as a total panel failure. - If the backend returns HTTP 400 with an empty body on panel query, verify, or create, assume a DTO-shape mismatch first and recheck the typed schema output before retrying.
refreshIntervalbelongs inparamson the object that owns refresh behavior, not in an arbitrary top-level field.- Creating a panel does not place it into a dashboard automatically; a separate dashboard update is still required.
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.
- 9d ago First seen · 119 lines · 29 tokens per session scan A 009bd3d239d3
idmp-panel is a skill published in the GitHub repository taosdata/agent-skills (3 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,974 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…