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 ADIKANT/datalens-dev-mcp --skill datalens-editorgit clone --depth 1 https://github.com/ADIKANT/datalens-dev-mcpWrote 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/adikant/datalens-dev-mcp/datalens-editor)<a href="https://agentmods.dev/skills/adikant/datalens-dev-mcp/datalens-editor"><img src="https://agentmods.dev/badge/skills/adikant/datalens-dev-mcp/datalens-editor/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/adikant/datalens-dev-mcp/datalens-editor"><img src="https://agentmods.dev/badge/skills/adikant/datalens-dev-mcp/datalens-editor.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.00028 | $0.00365 |
| Opus 5 | $0.00014 | $0.00182 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
datalens-editor 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 today.
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.
What it actually says
DataLens Editor
Read references/editor-authoring.md before compiling or validating Editor objects.
Select the actual Editor variant (table_node, d3_node, advanced-chart_node, markdown_node, or control_node) and preserve it on update. Use dl_compile_recipe for a registered visual family so the canonical renderer is reused; change bindings and allowed presentation values instead of regenerating large JavaScript. The tool materializes the complete draft in private local state and returns a compact draft_reference; pass that reference directly to validation/create, or combine its artifact_path only with update target identity and fresh revision, instead of reading and echoing the renderer. Use dl_editor_validate for static tabs, aliases and constrained-runtime checks. Report browser/live evidence separately.
Preserve the existing Editor technology. Resolve declared Meta aliases, Sources, Prepare, Config, Controls, Params, and wrapped render functions according to the selected chart type. Use short Dataset or direct QL/API source bindings where applicable. Keep missing alias, upstream error, and a valid empty result distinct. Use packaged reusable recipes for repeated visual families; do not regenerate their large JavaScript implementation for each task.
Follow authorized scope and delivery for mutations: explicit scoped work continues without repeated permission questions; read-only and save-only limits remain binding.
For new visual or semantic decisions, consult only the relevant part of visualization decisions; preserve the accepted reference and infer routine context without a mandatory questionnaire.
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.
- today Changed · +4 lines 650cd26e6614
- yesterday First seen · 13 lines · 28 tokens per session scan A 55b5b164ba73
datalens-editor is a skill published in the GitHub repository ADIKANT/datalens-dev-mcp (5 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 365 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-09-08.
Other skills, from other repositories
scrape-batch
Extract many known URLs in one polite, rate-limited pass. Use when the user hands over a list of links, a set of search hits to read in full, or asks to "scrape these pages" / "pull the content from all of them". Drives extract(action="batch"), which fans out with per-domain rate limiting and returns partial results…
compare
Structured comparison of 2+ alternatives with consistent criteria and decision matrix.
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
temporal-query
Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
recall-context
Use at session start, before significant decisions, or when a new task references a known project to recall mnemo memories matching the current working directory, recently edited files, or topic keywords. Helps maintain continuity across sessions and avoid redoing past research.