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/microsoft/powerplatform-dataverseclient-python/dataverse-sdk-usenpx skills add microsoft/PowerPlatform-DataverseClient-Python --skill dataverse-sdk-usegit clone --depth 1 https://github.com/microsoft/PowerPlatform-DataverseClient-PythonWhat 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 | $0.00041 | $0.06163 |
| Opus 5 | $0.00020 | $0.03082 |
| Sonnet 5 | $0.00008 | $0.01233 |
| Haiku 4.5 | $0.00004 | $0.00616 |
Grade A, and why
dataverse-sdk-use 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 2d 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 — 725 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerPlatform Dataverse SDK Guide
Overview
Use the PowerPlatform Dataverse Client Python SDK to interact with Microsoft Dataverse.
Key Concepts
Schema Names vs Display Names
- Standard tables: lowercase (e.g.,
"account","contact") - Custom tables: include customization prefix (e.g.,
"new_Product","cr123_Invoice") - Custom columns: include customization prefix (e.g.,
"new_Price","cr123_Status") - ALWAYS use schema names (logical names), NOT display names
Operation Namespaces
client.records-- CRUD and OData queriesclient.query-- query and search operationsclient.tables-- table metadata, columns, and relationshipsclient.files-- file upload operationsclient.batch-- batch multiple operations into a single HTTP request
Bulk Operations
The SDK supports Dataverse's native bulk operations: Pass lists to create(), update() for automatic bulk processing, for delete(), set use_bulk_delete when passing lists to use bulk operation
Paging
- Control page size with
page_sizeparameter onrecords.list(),records.list_pages(), orQueryBuilder.page_size() - Use
topparameter to limit total records returned - Preferred:
client.query.builder(table)....execute_pages()— composablewhere(col(...))filters, formatted values, expand with nested selects, full pagination control - Simple streaming shortcut:
records.list_pages(table, *, filter, select, top, orderby, expand, page_size, count, include_annotations)— string-based OData filter only, yields oneQueryResultper page execute(by_page=True/False)is deprecated and emitsUserWarning; useexecute_pages()insteadQueryBuilder.to_dataframe()is deprecated; use.execute().to_dataframe()instead
QueryResult
- Returned by
records.list(),records.retrieve(),execute(), and each page fromlist_pages()/execute_pages() - Iterable:
for record in result— each item is adict-likeRecord .to_dataframe()— convert to pandas DataFrame.first()— return the first record orNone(safe: returnsNoneon empty result)result[n]— index access returns aRecord;result[n:m]returns aQueryResultlen(result)— number of records in this result/page
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.
- 2d ago First seen · 725 lines · 41 tokens per session scan A 79e6e13016de
dataverse-sdk-use is a skill published in the GitHub repository microsoft/PowerPlatform-DataverseClient-Python (59 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 6,163 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…