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-elementgit 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-element)<a href="https://agentmods.dev/skills/taosdata/agent-skills/idmp-element"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/idmp-element.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.00029 | $0.01578 |
| Opus 5 | $0.00015 | $0.00789 |
| Sonnet 5 | $0.00006 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
idmp-element 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
element
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 |
Browse elements under the current parentId. |
+get |
Confirm one element after search or path lookup. |
+tree |
Inspect child nodes and tree structure. |
+search |
Find elements by keyword, root, or parent filters. |
What this skill solves
- Find a reliable
elementIdbefore downstream create or update work. - Resolve the full path so
rootElementIdcomes from the business root, not from the current leaf element. Proof: pairelement elements pathwithelement fullpath getand confirm the root is a first-level owner or an explicitly confirmed ancestor. - Reverse-check a resolved path with
by-pathbefore handing it to another workflow. - Read child templates before hierarchy-based analysis or panel work.
- Discover the current shared first-level root from live reads instead of assuming a historical
demotree is still present. - Distinguish plain container create from template-backed create before downstream analysis, panel, or alert workflows.
Element create paths
element.elements.createis for plain container elements. Use it when you need a parent node without template-backed metrics.element.new.createis for template-backed elements. Use it when the payload needstemplateIdandkeywordValues.- If the template is keyword-backed, confirm the upstream source table already exists before treating the new element as data-bearing.
Evidence of completion
- A container create is only complete after
element elements getorelement elements listrereads the new node under the intended parent. - A path-resolution task is only complete after
element elements path,element fullpath get, andelement by-path listagree on the same root-to-leaf record. - A template-backed create is only complete after reread proves the final template binding and keyword values survived the write.
What ships with it
4 files 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 · 106 lines · 29 tokens per session scan A 84ee5a7ab077
idmp-element is a skill published in the GitHub repository taosdata/agent-skills (3 stars, last pushed 24d ago), licensed MIT. It adds 29 tokens to every session and 1,578 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…