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 williamzujkowski/standards --skill secrets-managementgit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/williamzujkowski/standards/secrets-management)<a href="https://agentmods.dev/skills/williamzujkowski/standards/secrets-management"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/secrets-management/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/skills/williamzujkowski/standards/secrets-management"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/secrets-management.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.00048 | $0.03420 |
| Opus 5.5 | $0.00019 | $0.01368 |
| Sonnet 5.5 | $0.00010 | $0.00684 |
| Haiku 4.5 | $0.00005 | $0.00342 |
Grade A, and why
secrets-management scanned grade A 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets Management Security
Quick Navigation: Level 1: Quick Start (5 min) → Level 2: Implementation (30 min) → Level 3: Mastery (Extended)
Level 1: Quick Start (<2,000 tokens, 5 minutes)
Core Principles
- Never Hardcode Secrets: Use environment variables, secret management systems, or secure vaults
- Rotate Regularly: Implement automated rotation policies for all secrets
- Detect and Prevent: Use pre-commit hooks and scanning tools to prevent secret leaks
- Least Privilege: Grant minimum required access to secrets
- Encrypt Everywhere: Encrypt secrets at rest and in transit
Essential Checklist
- No secrets in code: All secrets stored externally (Vault, env vars, secrets manager)
- Pre-commit hooks: git-secrets or TruffleHog configured to prevent commits
- Environment variables: .env files used locally, never committed to git
- Secret rotation: Automated rotation policies implemented
- Access control: RBAC/ABAC policies enforce least privilege access
- Audit logging: All secret access logged with timestamps and user IDs
- Certificate management: TLS/mTLS certificates managed centrally
- Detection tools: Regular scans with multiple tools (TruffleHog, git-secrets, Gitleaks)
Quick Example
# @nist sc-12 "Cryptographic key management"
# @nist sc-13 "Cryptographic protection"
import os
from hashicorp_vault import VaultClient
from cryptography.fernet import Fernet
# ❌ NEVER do this
# API_KEY = "sk-1234567890abcdef"
# DATABASE_PASSWORD = "my_secure_password"
# ✅ Use environment variables
API_KEY = os.getenv('API_KEY')
if not API_KEY:
raise ValueError("API_KEY environment variable not set")
# ✅ Use HashiCorp Vault for sensitive secrets
vault = VaultClient(url=os.getenv('VAULT_ADDR'), token=os.getenv('VAULT_TOKEN'))
db_credentials = vault.read_secret('database/prod')
DB_PASSWORD = db_credentials['password']
# ✅ Encrypt sensitive data
def encrypt_sensitive_data(data: str) -> bytes:
"""Encrypt sensitive data using Fernet symmetric encryption."""
key = os.getenv('ENCRYPTION_KEY').encode()
cipher = Fernet(key)
return cipher.encrypt(data.encode())
# ✅ Never log secrets
def authenticate_api(api_key: str):
"""Authenticate with API using key."""
# Log without exposing secret
print(f"Authenticating with key: {api_key[:8]}...") # Only show prefix
What ships with it
11 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.
- .githooks/pre-commit 8.1 KB
- config/vault-config.hcl 6.8 KB
- resources/configs/.pre-commit-secrets.yaml 923 B
- resources/detection-tools.md 3.5 KB
- resources/README.md 35 B
- scripts/README.md 33 B
- scripts/rotate-secrets.sh 10 KB runs code
- templates/.env.example 2.9 KB
- templates/.env.template 5.9 KB
- templates/README.md 35 B
- templates/vault-config.hcl 817 B
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.
- yesterday First seen · 473 lines · 48 tokens per session scan A 44a101bb8c50
secrets-management is a skill published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 3,420 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-29.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…