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 OKHP3/skillz --skill secrets-managementgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/secrets-management)<a href="https://agentmods.dev/skills/okhp3/skillz/secrets-management"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/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/okhp3/skillz/secrets-management"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/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.00086 | $0.01184 |
| Opus 5 | $0.00043 | $0.00592 |
| Sonnet 5 | $0.00017 | $0.00237 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
secrets-management 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets management
A secret's danger is proportional to how many places it exists and how long it lives. Most practice focuses on the first storage decision and ignores rotation and revocation, which is where the real exposure sits — a key nobody has rotated in four years has been on more laptops than anyone can name.
Assume every secret will eventually leak. Design so that when it does, the blast radius is small and the fix is one command.
1. Prefer not having a secret at all
The best credential is one that does not exist. In order of preference:
- Workload identity, the platform vouches for the service. IAM roles, service accounts, OIDC federation. Nothing to store, nothing to rotate, nothing to leak
- Short-lived credentials issued on demand, expiring in minutes or hours
- A long-lived secret in a manager, injected at runtime
- A long-lived secret in an environment variable — workable, and the floor
- A secret in a file in the repo, never
Most cloud-to-cloud authentication can use option 1 today, and teams keep using static keys out of habit. That is the single biggest available improvement.
Done when: every static credential has been checked for a workload-identity alternative.
2. Never let a secret near the repository
- Not in code, config, or a committed
.env. Commit a.env.examplewith empty values - Not in a Dockerfile
ARGorENV. Layers are permanent and readable withdocker history, even if a later layer deletes it - Not in CI config, only in the platform's secret store
- Not in a log line, error message, URL, or trace. Redact at the logging boundary, not at each call site, or one new code path leaks everything
- Not in a ticket, chat message, or screenshot. These are searched and archived
Run a scanner in CI and as a pre-commit hook — gitleaks, trufflehog, or the platform's own.
It is cheap and it catches the mistake before it becomes permanent.
Done when: a scanner runs on every commit and the history is clean.
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.
- 6d ago First seen · 110 lines · 86 tokens per session scan A 7f73b009fa9c
secrets-management is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,184 once invoked, about $0.0004 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
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
pm-aarrr
A post-launch product-growth workflow based on AARRR: acquiring users, activating them, retaining them, earning revenue, and gaining referrals.
pm-docs
A workflow for producing product documents such as PRDs, BRDs, and MRDs. These are structured documents describing what a product needs, its business case, and its market.
product-marketing-copywriter
A marketing-copy tool that analyzes audience problems and product benefits, then creates promotional headlines and body text. Marketing copy is writing intended to explain and promote a product.
pm-position
A guided process for defining a product’s market position, value, audience, competitive difference, business model, pricing, and revenue plan. The instructions are written mainly in Chinese.
pm-retro
A retrospective workflow for reviewing a finished agile iteration, recording what happened, and choosing improvements for the next cycle.