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-catalog-explorenpx skills add ahmedawan-oracle/claude-code-plugins --skill aidp-catalog-exploregit 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-catalog-explore)<a href="https://agentmods.dev/skills/ahmedawan-oracle/claude-code-plugins/aidp-catalog-explore"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/aidp-catalog-explore.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.1 | $0.00081 | $0.01161 |
| Opus 5 | $0.00041 | $0.00580 |
| Sonnet 5 | $0.00016 | $0.00232 |
| Haiku 4.5 | $0.00008 | $0.00116 |
Grade A, and why
aidp-catalog-explore 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aidp-catalog-explore — live catalog browsing
Browse and inspect the AIDP catalog directly via the control-plane — no SQL, no compute, no MCP required.
Complements aidp-catalog-init: use this for ad-hoc, live lookups; use catalog-init to build the cached
grounding file.
When to use
- "What catalogs/schemas/tables are there?" · "describe / show columns of " · "find tables about X"
- You need a catalog/schema/table key to feed another skill.
Engine — official aidp CLI (control-plane, read-only)
Preferred engine is the official Oracle aidp CLI; oci raw-request is the fallback when the CLI isn't
installed. Both hit the same data-plane REST API with the same auth — see
references/aidp-cli-map.md for the full command map and
references/oci-raw-request.md for base URL + auth ladder.
| Goal | CLI (preferred) | REST fallback (verified) |
|---|---|---|
| List catalogs | aidp catalog list |
GET /catalogs |
| Describe a catalog | aidp catalog get --catalog-key <cat> |
(in list output) |
| List schemas in a catalog | aidp schema list --catalog-key <cat> |
GET /schemas?catalogKey=<cat> |
| List tables in a schema | aidp schema list-tables --catalog-key <cat> --schema-key <cat.schema> |
GET /tables?catalogKey=<cat>&schemaKey=<cat.schema> |
| Describe a single table | aidp schema get-table --catalog-key <cat> --schema-key <cat.schema> --table-key <t> |
GET /tables?… then filter by table key client-side |
| List volumes | aidp volume list --catalog-key <cat> |
GET /volumes?catalogKey=<cat> (param shape TBD — if 400, the error names the required param) |
All CLI calls take --instance-id <DATALAKE_OCID> --auth api_key --profile DEFAULT --region <r>.
# CLI (preferred): list tables in cat.schema
aidp schema list-tables --catalog-key default --schema-key default.default \
--instance-id <DATALAKE_OCID> --auth api_key --profile DEFAULT --region us-ashburn-1
# Fallback (no CLI installed): oci raw-request, --profile DEFAULT (api_key)
oci raw-request --http-method GET \
--target-uri "https://aidp.us-ashburn-1.oci.oraclecloud.com/20240831/dataLakes/<OCID>/tables?catalogKey=default&schemaKey=default.default" \
--profile DEFAULT
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.
- 5d ago First seen · 68 lines · 81 tokens per session scan A 74875d787573
aidp-catalog-explore is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,161 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
pinecone
Managed vector DB for production RAG and search.
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
cognee-community
Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify)…
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
ingesting-into-data-lake
Import data into the AWS data lake from S3 files, local uploads, JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS, Aurora), Amazon Redshift, Snowflake, BigQuery, DynamoDB, or existing Glue catalog tables (migration). Default target is S3 Tables; standard Iceberg on a general purpose bucket is supported where…