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 ballerina-platform/ballerina-vscode --skill data-mapgit clone --depth 1 https://github.com/ballerina-platform/ballerina-vscodeWrote 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/ballerina-platform/ballerina-vscode/data-map)<a href="https://agentmods.dev/skills/ballerina-platform/ballerina-vscode/data-map"><img src="https://agentmods.dev/badge/skills/ballerina-platform/ballerina-vscode/data-map/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/ballerina-platform/ballerina-vscode/data-map"><img src="https://agentmods.dev/badge/skills/ballerina-platform/ballerina-vscode/data-map.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.00060 | $0.01759 |
| Opus 5.5 | $0.00024 | $0.00704 |
| Sonnet 5.5 | $0.00012 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
data-map 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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mapping Request
$ARGUMENTS
Interpret the request above using whichever of these patterns fits:
- "generate mappings for the function" → function mode; the function name is the word immediately before "function".
- "generate mappings using input as and output as using the function" → records mode; create a new transform function with that signature.
- "generate mappings using record fields and external values" → inline mode; derive the output type from "Output type: " in the hidden context.
- A single function name (no surrounding text) → function mode; fill out the existing function with the mapping.
- A single record/type name with no surrounding text and no function context → inline mode; produce inline field expressions, not a function body.
- Empty (literal
$ARGUMENTSleft in place) → derive everything from the current file context provided in the hidden context.
Priority Hierarchy
When generating mapping expressions, follow this strict priority order:
- User-defined mappings — ABSOLUTE HIGHEST PRIORITY. Complete precedence over everything else.
- Existing sub-mappings — use the sub-mapping output name as a direct reference.
- Context and constraints — apply all provided business rules and transformation logic.
- Ballerina programming knowledge — use built-in functions and standard approaches.
- Default handling — only for non-optional fields when no mapping is available.
Mapping Output Modes
There are two distinct mapping modes. Choose the correct one based on the task:
Mode 1 — Transform Function (reusable mapping)
When implementing a named Ballerina transform function, you MUST use the expression body syntax with =>. This is critical: the => expression body is what the Ballerina tooling uses to classify the function as a Data Mapper. A block-body function with return will be placed under "Functions" instead of "Data Mappers" and will not work as a data mapper.
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.
- 3d ago First seen · 123 lines · 60 tokens per session scan A 854df05834d9
data-map is a skill published in the GitHub repository ballerina-platform/ballerina-vscode (49 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 1,759 once invoked, about $0.0002 per session on Opus 5.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-10-26.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…