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 ikenga-hq/ikenga-pkgs --skill querygit clone --depth 1 https://github.com/ikenga-hq/ikenga-pkgsWrote 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/ikenga-hq/ikenga-pkgs/query)<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/query"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/query.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.00131 | $0.00854 |
| Opus 5 | $0.00066 | $0.00427 |
| Sonnet 5 | $0.00026 | $0.00171 |
| Haiku 4.5 | $0.00013 | $0.00085 |
Grade A, and why
query 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
query — cross-domain reader skill
This file is a router. The single action lives in actions/query.md.
The state contract (which ikenga.db tables are readable, SELECT-only boundary)
is in lib/state.md — read it before authoring or modifying the action.
skill-core note:
depends_on: ['skill-core']is declared above.skill-coreis not yet packaged (Phase 3+). skill-query declares the dependency edge now (per the G-04 contract and the lint spec in06-skill-action-contract.md§5) so the graph is correct from day one; the dependency resolves when skill-core ships. Per the lint, no other target is legal.
Purpose (one line)
Translate operator questions into parameterised SELECTs over ikenga.db and
stream the answer — reading all declared domain tables, writing nothing.
Actions
| Action | File | Mode | One-liner |
|---|---|---|---|
query |
actions/query.md |
streaming |
Translate a natural-language question into SQL SELECTs; stream the formatted answer. |
No setup action — skill-query has no per-project instance state. It reads; it
does not configure. No digest/report action — recurring briefings stay with
skill-pa briefing (P5 dedup).
Routing
| If the operator asks… | Load | Then |
|---|---|---|
| Any question about data: "how many tasks…", "show me deals…", "what revenue…", "which content…" | actions/query.md |
Translate → parameterised SELECT → stream answer |
Do not route here for:
- Task/email/deal create, edit, delete, reassign → domain pkgs
- Morning briefing, EOD summary, weekly digest →
skill-pa briefing - Dispatching sends, approving drafts → domain pkgs
What skill-query does NOT do
- No writes —
host.dbExecis never called. Zero INSERT/UPDATE/DELETE/DROP. - No dispatch — no side effects, no queue commits.
- No digest — interactive questions only; scheduled aggregations belong to
skill-pa briefing. - No cross-domain aggregation as a lib — panes compute their own KPIs client-side; this skill is for operator questions in the dock chat.
- No Supabase — state is local
ikenga.dbviahost.dbQuerySELECT-only.
What ships with it
2 files 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 · 96 lines · 131 tokens per session scan A fcb7d09df762
query is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed today), licensed Apache-2.0. It adds 131 tokens to every session and 854 once invoked, about $0.0007 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
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…