Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chambear2809/splunk-cisco-skillsnpx agentmods add rules/chambear2809/splunk-cisco-skills/credential-handlingWrote 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/chambear2809/splunk-cisco-skills/credential-handling)<a href="https://agentmods.dev/rules/chambear2809/splunk-cisco-skills/credential-handling"><img src="https://agentmods.dev/badge/rules/chambear2809/splunk-cisco-skills/credential-handling/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/chambear2809/splunk-cisco-skills/credential-handling"><img src="https://agentmods.dev/badge/rules/chambear2809/splunk-cisco-skills/credential-handling.svg" alt="Reviewed on agentmods" width="80" 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.00616 | $0.00616 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade B, and why
credential-handling scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
(chmod 600, gitignored) and read automatically by all skill scripts via the How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure Credential Handling
Agent Rules
-
NEVER ask the user for passwords, API keys, tokens, client secrets, or any other secret in conversation. This includes Splunk credentials, device passwords, Meraki API keys, Intersight client secrets, Splunkbase passwords, and any other sensitive value.
-
NEVER pass
SPLUNK_USER,SPLUNK_PASS,SB_USER,SB_PASS, or any secret as an environment variable prefix in shell commands. For example, do NOT run:SPLUNK_PASS="secret" bash script.sh -
NEVER pass secrets as command-line arguments (e.g.,
--password mysecret). Use file-based alternatives instead (--password-file /path/to/file). -
Splunk credentials are stored in the project-root
credentialsfile (chmod 600, gitignored) and read automatically by all skill scripts via the shared credential helper library atskills/shared/lib/credential_helpers.sh. The library also falls back to~/.splunk/credentialsif the project file does not exist. -
If Splunk credentials are not yet configured, guide the user to run:
bash skills/shared/scripts/setup_credentials.shOr copy and edit the example:
cp credentials.example credentials && chmod 600 credentials -
Device credentials (device passwords, API keys, client secrets) should be handled by instructing the user to create a temporary file without putting the secret in shell history:
bash skills/shared/scripts/write_secret_file.sh /tmp/secret_fileThen pass the file path to the script (e.g.,
--password-file /tmp/secret_file). Instruct the user to delete the file after use. -
You MAY freely ask for non-secret values: account names, hostnames, IP addresses, regions, index names, organization IDs, client IDs, and other configuration values that are not credentials.
Script Patterns
All scripts under skills/ source the shared library via a relative path:
source "${SCRIPT_DIR}/../../shared/lib/credential_helpers.sh"
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.
- 5d ago First seen · 64 lines · 616 tokens per session scan B cf3995b19e07
credential-handling is a cursor rule published in the GitHub repository chambear2809/splunk-cisco-skills (37 stars, last pushed 4d ago), licensed Apache-2.0. It adds 616 tokens to every session, about $0.0031 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.