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 sleeyax/promptfiles --skill oc-query-dbgit clone --depth 1 https://github.com/sleeyax/promptfilesWrote 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/sleeyax/promptfiles/oc-query-db)<a href="https://agentmods.dev/skills/sleeyax/promptfiles/oc-query-db"><img src="https://agentmods.dev/badge/skills/sleeyax/promptfiles/oc-query-db.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.00042 | $0.02117 |
| Opus 5 | $0.00021 | $0.01059 |
| Sonnet 5 | $0.00008 | $0.00423 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
oc-query-db 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 7d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query a Database on OpenShift
Question: $ARGUMENTS
Follow the steps in order. Every query is logged, runs under the user's own oc login, and touches real data belonging to real people. When a step says to ask the user, ask — never guess.
Allowed commands
oc whoamiandoc project -q.oc getandoc describeon pods and workloads in the target namespace.oc execinto the database pod, for exactly two commands: theprintenvlisting in step 3 and the query template in step 4.- SQL that passes the checklist in step 6.
For anything else: tell the user the command and let them run it themselves.
Step 1: Preflight
oc whoami >/dev/null
NS=$(oc project -q)
- If
oc whoamifails: stop and ask the user to runoc login. - Keep the
>/dev/null: you only need the exit code, and the identity it would print is the user's, not yours to record. - If the user named a namespace: set
NSto that name instead. - From here on, put
-n "$NS"on everyoccommand. That leaves the user's ownoccontext untouched.
Done when oc whoami succeeded and NS is set.
Step 2: Find the database pod
oc -n "$NS" get mariadb -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.currentPrimary}{"\n"}{end}'
Each output row is <resource-name> <pod-name>, where the pod is that resource's current primary.
-
Exactly one row: use its pod.
-
Several rows: filter with a command, never by judgment. Take the word the user used to name the database, lowercase it, and rerun the listing through a whole-word filter — this example is for the word
remi:oc -n "$NS" get mariadb -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.currentPrimary}{"\n"}{end}' | grep -E "(^|[-_])remi([-_]|$)"Put the user's word where
remiis; change nothing else in the regex. The filter keeps whole-word matches only: forremiit keepsremi-backend-mariadband dropsremini-db. Exactly one row survives: use its pod. Zero or several rows survive: list all the resources and ask the user which one. -
No rows: stop and report that the namespace has no MariaDB resource.
What ships with it
1 file 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.
- 7d ago First seen · 154 lines · 42 tokens per session scan A bf902851f40b
oc-query-db is a skill published in the GitHub repository sleeyax/promptfiles (2 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 2,117 once invoked, about $0.0002 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
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…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.