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 rules/alphabitcore/nexus-gateway/useapi-querykeygit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWhat 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.00000 | $0.00412 |
| Opus 5 | $0.00000 | $0.00206 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
useapi-querykey 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 2d 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.
What it actually says
useApi queryKey requires a domain prefix (binding)
Every useApi(fetcher, queryKey) call must start queryKey with at least two string literals that uniquely identify the endpoint, followed by any state variables that affect the fetcher.
Required shape
['admin' | 'my' | 'user' | 'proxy', '<resource>', '<variant?>', ...stateVars]
Forbidden
useApi(fetcher, []) // ❌ empty
useApi(fetcher, [debouncedSearch, offset, pageLimit]) // ❌ no domain prefix
useApi(fetcher, [id]) // ❌ single var
Correct
useApi(fetcher, ['admin', 'routing-rules', 'list', search, enabled, offset, limit])
useApi(fetcher, ['admin', 'policies', 'detail', id])
useApi(fetcher, ['admin', 'providers', 'list', 'model-list-picker']) // usage-suffix disambiguates
Why
React Query stores under ['api', ...queryKey]. Pages with the same state shape (e.g. ['', '', 0, 20]) collide in the cache. Navigating from one list to another shows the previous page's data with the new page's columns — a confusing class of UI bug.
When the same API is fetched from multiple call sites intentionally (e.g., providers list used by ModelList and CredentialList), add a usage-site suffix to each call so the two callers dedupe only within themselves and do not leak stale data into unrelated pages.
Skipping this rule requires explicit user approval in chat.
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan A f0debe6776e5
useapi-querykey is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 412 tokens. 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-30.
Other cursor rules, from other repositories
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
flagship_author
How to author a flagship in ks-cookbook.
recipe_author
How to author a recipe in ks-cookbook.
30-framework-routing
Route tasks to HIPAA, HITECH, PCI-DSS, SOC 2, ISO 27001, NIST CSF, NIST AI RMF, FERPA, COPPA, CCPA, US state privacy, GDPR, FedRAMP, SOX, CMMC, and GLBA skills based on user intent and presets.
00-compliance-agent-core
Core compliance agent mission, PHI redaction gate, and audit lifecycle for HIPAA, PCI-DSS, and SOC 2.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.