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 korchard333/claude-power-platform-community --skill dataversegit clone --depth 1 https://github.com/korchard333/claude-power-platform-communityWrote 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/korchard333/claude-power-platform-community/dataverse)<a href="https://agentmods.dev/skills/korchard333/claude-power-platform-community/dataverse"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/dataverse/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/korchard333/claude-power-platform-community/dataverse"><img src="https://agentmods.dev/badge/skills/korchard333/claude-power-platform-community/dataverse.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.00051 | $0.00696 |
| Opus 5 | $0.00026 | $0.00348 |
| Sonnet 5 | $0.00010 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
dataverse 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Dataverse Schema & Data Modeling
When to Use
Trigger when designing tables, columns, relationships, security roles, views, or querying Dataverse via OData/FetchXML.
Table Type Selection
| Factor | Standard Table | Elastic Table | Virtual Table |
|---|---|---|---|
| Data volume | < 10M rows | 10M+ rows, high write throughput | External data (no copy) |
| Transactions | Full ACID (multi-record) | Per-record only | None |
| Security | Full row/column | Organization-owned only | Organization-owned only |
| BPF support | Yes | No | No |
| Charts/dashboards | Yes | No | No |
| Calculated/rollup | Yes | No | No |
| TTL auto-expiry | No | Yes | N/A |
| Offline support | Yes | No | No |
| Best for | Business data, CRUD apps | IoT, logs, telemetry, high-volume ingestion | Read-only external data (SQL, SharePoint, Fabric) |
⚠️ REQUIRED: Load Sub-Files Before Implementation
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
- Table Design — Table design principles, column type guide, auto-number columns, alternate keys
- Relationships — N:1, 1:N, N:N, manual intersect tables, cascade behaviors
- Query Patterns — OData queries, FetchXML, lookup handling in Code Apps, schema discovery via metadata API
- Naming Conventions — Publisher prefix, table/column/relationship naming standards
- Elastic & Virtual Tables — Elastic tables (Cosmos DB), virtual tables, Dataverse search, long-term retention
Anti-Patterns
- Text columns used as primary identifiers without alternate keys
- Cascade delete without documenting intended behavior
- Org-owned tables where row-level security is needed
- Rollup columns on tables with millions of rows
- Storing JSON blobs in text columns to avoid proper schema
- Duplicate choice definitions across tables (use global option sets)
- N:N relationship used when the intersect needs attributes
- Missing indexes on frequently-filtered lookup columns
- Over-permissive security roles ("just give them System Admin")
What ships with it
5 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.
- 9d ago First seen · 63 lines · 51 tokens per session scan A f48986a79e7e
dataverse is a skill published in the GitHub repository korchard333/claude-power-platform-community (47 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 696 once invoked, about $0.0003 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…