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-bundlenpx skills add ahmedawan-oracle/claude-code-plugins --skill aidp-bundlegit 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-bundle)<a href="https://agentmods.dev/skills/ahmedawan-oracle/claude-code-plugins/aidp-bundle"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/aidp-bundle.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.00077 | $0.02491 |
| Opus 5 | $0.00039 | $0.01246 |
| Sonnet 5 | $0.00015 | $0.00498 |
| Haiku 4.5 | $0.00008 | $0.00249 |
Grade A, and why
aidp-bundle 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aidp-bundle — resource bundles (Preview)
Deploy/manage AIDP resource bundles. CLI (preferred): the official aidp bundle … CLI
(Oracle-supported, versioned — see references/aidp-cli-map.md):
aidp bundle create | deploy | fetch-deployment-status | purge | sync-bundle.
Fallback: oci raw-request against the same REST Bundle API (auth + base URL in
references/oci-raw-request.md) when the CLI isn't installed.
Self-contained: no MCP and no ai-data-engineer-agent repo required.
Preview + verify-first (no-fabrication):
Bundleis Preview. On this env (20240831,dataLakes) the Bundle resource may be not provisioned — expect a404(wrong version/prefix or feature not enabled in the tenancy). Confirm with a live read-onlygetDeploymentStatusbefore any deploy/purge, and record the result inreferences/rest-endpoint-map.md. Do not present endpoints as confirmed until a live 2xx (or documented 4xx) is recorded.
When to use
- "Deploy these resources together", "promote a bundle", "what's the deployment status", "purge/tear down a bundle".
Commands / endpoints (workspace-scoped; Preview)
CLI (preferred): aidp bundle create · aidp bundle deploy · aidp bundle fetch-deployment-status
(read-only — verify here) · aidp bundle purge · aidp bundle sync-bundle.
Fallback (oci raw-request) — default 20240831, probe 20260430 only after a tenancy upgrade.
Base: https://aidp.<region>.oci.oraclecloud.com/20240831/dataLakes/<DATALAKE_OCID>/…
POST /workspaces/{ws}/bundles— createPOST /workspaces/{ws}/bundles/actions/deploy— deploy all resourcesPOST /workspaces/{ws}/bundles/actions/getDeploymentStatus— status (read-only — verify here)POST /workspaces/{ws}/bundles/actions/purge— destroy deployed resources
A
404(REST) or not-provisioned error (CLI) on any of these means not provisioned in this tenancy (or wrong version/prefix — try the other per references/oci-raw-request.md), not that the request was malformed. Report it as a feature-availability gap, not a failure.
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 · 136 lines · 77 tokens per session scan A 64f8bdd7a3a4
aidp-bundle is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 2,491 once invoked, about $0.0004 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…