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/secrets-env-onlygit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWrote 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/rules/alphabitcore/nexus-gateway/secrets-env-only)<a href="https://agentmods.dev/rules/alphabitcore/nexus-gateway/secrets-env-only"><img src="https://agentmods.dev/badge/rules/alphabitcore/nexus-gateway/secrets-env-only.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.00000 | $0.00393 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
secrets-env-only 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.
What it actually says
Secrets are env-only — never YAML (binding)
No secret field may appear in any YAML committed to the repo. Secrets ride env variables, documented in .env.example at repo root, read at runtime via os.Getenv / bootenv.
Forbidden in committed YAML
- Auth tokens.
- HMAC keys.
- Credential-encryption keys / passphrases / salts.
- Internal-service tokens.
- DB passwords.
- Any field named
secret/password/token/keycarrying a real value.
Allowed in committed YAML
- Service shape (ports, timeouts, feature flags, log levels, allowlists).
- Non-secret tunings.
- Empty/placeholder fields that get overridden by env at boot — but every such field has a corresponding env var in
.env.example.
Cross-service shared secrets
When two services share a secret (e.g., inter-service HMAC), tag both env-var lines in .env.example with [MUST MATCH]. Drift between consumers is the most common source of inter-service 403s.
Adding a new secret YAML field
Forbidden by default. Requires explicit user approval in chat with a stated reason (real reason — "it's easier" is not valid).
Operational detail
- Local: repo-root
.envloaded viabootenv. - Prod: systemd
EnvironmentFile=or K8s Secret. - Full operational rules:
docs/developers/workflow/local-dev-debugging.md"Environment variables" — that section carries the same binding force as this file.
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.
- 4d ago First seen · 44 lines · 0 tokens per session scan A 7ea196741471
secrets-env-only is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 393 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.