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-credentialsnpx skills add ahmedawan-oracle/claude-code-plugins --skill aidp-credentialsgit 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-credentials)<a href="https://agentmods.dev/skills/ahmedawan-oracle/claude-code-plugins/aidp-credentials"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/aidp-credentials.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.00100 | $0.01343 |
| Opus 5 | $0.00050 | $0.00672 |
| Sonnet 5 | $0.00020 | $0.00269 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
aidp-credentials 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aidp-credentials — credential store (Preview)
Manage centrally-stored AIDP credentials/secrets.
CLI (preferred): aidp credentials <command> --instance-id <DATALAKE_OCID> --auth api_key --profile DEFAULT --region <r>
aidp credentials list | get | create | update | delete
Fallback (no CLI): same credentialStore REST API via oci raw-request (identical endpoint + auth;
see references/oci-raw-request.md).
Preview + verify-first (no-fabrication):
credentialStoreis Preview and the route exists, but its GET/response shape is TBD. Confirm the working path (default20240831/dataLakes) with a liveaidp credentials list(orGET …/credentials) before asserting success or doing writes; record it inreferences/rest-endpoint-map.md. Treat the path as UNVERIFIED until a live 2xx returns.
When to use
- "Store/rotate a secret in AIDP", "manage connection credentials", "stop embedding this secret in code".
Workflow
- Verify first:
aidp credentials list(CLI) — or aGET …/credentials(REST fallback) — returns 2xx; record the version/prefix. - Read/create/update as asked. Never print secret values; pass secret material in the request body only, never echo it back. Confirm before delete/rotate.
- Handle async 202 + etag/if-match per the shared conventions.
Mutating ops (create, update/rotate, delete): persist the body to .aidp/payloads/ and confirm
first (references/payloads.md).
Create body — CreateDataLakeCredentialDetails
CLI: aidp credentials create <DATALAKE_OCID> --body <JSON> (CLI README "credentials create"). Top-level
envelope (SDK create_data_lake_credential_details.py:51-63):
| Field (wire) | Req | Notes |
|---|---|---|
displayName |
✅ | start with a letter; letters/digits/_ only — no secrets in the name |
credentialDescription |
– | purpose summary |
type |
✅ | discriminator — SECRET_TOKEN | VAULT_REFERENCE | SERVICE_ACCOUNT (…:18-26) |
credentialDetails |
✅ | nested object whose credentialType must match type (credential_details.py:52-73) |
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 · 86 lines · 100 tokens per session scan A 49d0d876dde7
aidp-credentials is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 1,343 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…