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/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/secrets-managerWrote 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/jansenanalytics/claudex/secrets-manager)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/secrets-manager"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/secrets-manager.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.00042 | $0.00440 |
| Opus 5 | $0.00021 | $0.00220 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
secrets-manager 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-manager
Manage secrets and environment variables securely: .env files, encrypted vaults, key rotation, secret scanning. Use when: setting up environment variables, managing API keys, rotating secrets, scanning repos for leaked credentials, or configuring secret storage.
Workflows
Generate .env file from template
bash scripts/env-generator.sh --template .env.example --output .env
Reads .env.example, prompts for missing values, writes .env with proper permissions (600).
Validate .env file
bash scripts/env-generator.sh --validate .env --template .env.example
Checks all required keys exist, flags empty values, warns about insecure patterns.
Scan repo for leaked secrets
bash scripts/secret-scanner.sh [directory]
Scans files for API keys, tokens, passwords, private keys using regex patterns. Respects .gitignore. Returns exit code 1 if secrets found.
Create .env template from existing .env
bash scripts/env-template-creator.sh .env > .env.example
Strips values, keeps keys and comments, adds type hints.
Scripts
| Script | Purpose |
|---|---|
scripts/env-generator.sh |
Generate and validate .env files |
scripts/secret-scanner.sh |
Scan repos for leaked secrets |
scripts/env-template-creator.sh |
Create .env.example from .env |
References
| File | Contents |
|---|---|
references/secret-patterns.md |
Regex patterns for detecting secrets |
references/env-best-practices.md |
.env file best practices and vault comparison |
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 · 61 lines · 42 tokens per session scan A 6053260d2514
secrets-manager is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 440 once invoked, about $0.0002 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-03.
Other skills, from other repositories
cis-aws-foundations-2.12
Ensure access keys are rotated every 90 days or less.
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to…
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to…
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to…
varlock
Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminal, logs, or LLM context. Provides guidance around integrating varlock into a project, reading/editing .env.schema and other .env files…
varlock-agent-readiness
Use this skill to discover machine-readable metadata published by varlock.dev.