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/ahmedawan-oracle/claude-code-plugins/aidp-data-sharingnpx skills add ahmedawan-oracle/claude-code-plugins --skill aidp-data-sharinggit clone --depth 1 https://github.com/ahmedawan-oracle/claude-code-pluginsWrote 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/ahmedawan-oracle/claude-code-plugins/aidp-data-sharing)<a href="https://agentmods.dev/skills/ahmedawan-oracle/claude-code-plugins/aidp-data-sharing"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/aidp-data-sharing.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 | $0.00098 | $0.00923 |
| Opus 5 | $0.00049 | $0.00462 |
| Sonnet 5 | $0.00020 | $0.00185 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
aidp-data-sharing 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aidp-data-sharing — Delta Sharing (shares & recipients)
Open data sharing over the Delta Sharing protocol via the AIDP DeltaShare API. A differentiator:
open-protocol sharing driven from the agent.
CLI (preferred): aidp delta-share <command> --instance-id <DATALAKE_OCID> --auth api_key --profile DEFAULT --region <r>
- Shares:
aidp delta-share create | get | list | update | delete | manage-access | manage-data-asset | manage-permission | list-data-assets - Recipients:
aidp delta-share create-recipient | get-recipient | list-recipients | update-recipient | delete-recipient | manage-recipient-permission | list-recipient-shares | list-recipient-permissions
Fallback (no CLI): same DeltaShare REST API via oci raw-request (identical endpoint + auth; see
references/oci-raw-request.md).
Verify-first:
GET /sharesandGET /recipientsare LIVE-VERIFIED 200 on20240831/dataLakes(auth--profile DEFAULT, api_key) —aidp delta-share list/list-recipientshit the same path. Default to that version/prefix; treat20260430as the future GA target and probe only after a tenancy upgrade. Confirm any write with a live response before destructive actions; record inreferences/rest-endpoint-map.md.
When to use
- "Share this table/schema with <team/org>", "set up Delta Sharing", "add/manage a recipient", "grant access to a share", "rotate a recipient token".
Workflow
- Verify with
aidp delta-share list(CLI) — orGET /shares(REST fallback; auth ladder inreferences/oci-raw-request.md). - Create a share → add data assets (
manage-data-asset, referencing real catalog tables fromaidp-catalog-explore) → create/attach recipients → manage access/permissions. - Recipient tokens: surface expiry; rotate via
update-recipient/manage-recipient-permission. Never print the recipient bearer token. - Confirm before granting access or deleting a share/recipient (outward-facing — data leaves the tenancy).
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.
- 4d ago First seen · 53 lines · 98 tokens per session scan A 73c11ebe6a1c
aidp-data-sharing is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 923 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…