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.
git clone --depth 1 https://github.com/CiscoDevNet/essentialsWrote 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/ciscodevnet/essentials/env-credentials)<a href="https://agentmods.dev/rules/ciscodevnet/essentials/env-credentials"><img src="https://agentmods.dev/badge/rules/ciscodevnet/essentials/env-credentials.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.00232 | $0.00232 |
| Opus 5 | $0.00116 | $0.00116 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
env-credentials 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
Environment Variables and Credentials
When a command fails due to missing environment variables or credentials, such as:
passphrase must be set with PULUMI_CONFIG_PASSPHRASEMissing required environment variableAPI key not foundAuthentication failedCredentials not configured
Do NOT tell the user to run commands in their own terminal.
Resolution Steps
- Check if a
.envfile exists in the current project directory - Ask the user: "I encountered a credentials/environment variable error. Can I source the
.envfile to get the required values?" - If approved, run commands by sourcing the .env first:
set -a && source .env && set +a && <command>
Security Notes
- Never read or display the contents of
.envfiles (they contain secrets) - Always verify
.envis gitignored before proceeding - The
.envfile should contain the required environment variables
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 · 34 lines · 232 tokens per session scan A 81d4dfca548c
env-credentials is a cursor rule published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 232 tokens to every session, about $0.0012 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-09-04.
Other cursor rules, from other repositories
solar
Rules for building with Solar (solarbuild) — a runtime UI framework for AI-generated code.
deployment
Deployment guidelines, Cloudflare Workers compatibility, and environment management.
docker-deployment
Complete Docker containerization, production deployment, and monitoring patterns for POS System.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.