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 agentmods add commands/nitinjain999/platform-skills/secretsgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/commands/nitinjain999/platform-skills/secrets)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/secrets"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/secrets.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.00031 | $0.04256 |
| Opus 5 | $0.00015 | $0.02128 |
| Sonnet 5 | $0.00006 | $0.00851 |
| Haiku 4.5 | $0.00003 | $0.00426 |
Grade A, and why
secrets 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sh -c 'wget -qO- http://localhost:8080/healthz || curl -sf http://localhost:8080/healthz' How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets Command
Structured guidance for secrets strategy, External Secrets Operator, Sealed Secrets, rotation, and Kubernetes-side secrets audit.
Activation
/platform-skills:secrets design # ESO vs Sealed Secrets decision; choose a strategy for the cluster
/platform-skills:secrets eso # ExternalSecret/SecretStore scaffold; debug sync errors
/platform-skills:secrets sealed # seal, rotate, backup master key; troubleshoot decryption failures
/platform-skills:secrets rotate # rotation runbook — update provider value, force sync, verify pods reload
/platform-skills:secrets audit # find bad SA tokens, unhealthy ExternalSecrets, missing secrets
Interactive Wizard (fires when no mode is provided)
When invoked with no arguments, ask before proceeding:
Q1 — Mode?
What do you need?
1. design — choose ESO vs Sealed Secrets for a cluster or workload
2. eso — scaffold ExternalSecret/SecretStore, or debug a sync error
3. sealed — seal a new secret, rotate an existing one, or back up the master key
4. rotate — end-to-end rotation runbook for a live secret
5. audit — find service account token secrets, unhealthy ExternalSecrets, plain secrets in Git
Enter 1–5 or mode name:
Q2 — Context (after mode selected):
- design:
What is the backend — AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, or no cloud provider? - eso:
Paste the ExternalSecret or SecretStore YAML, or describe the sync error. - sealed:
New secret or rotating an existing one? Which namespace? - rotate:
Which secret is rotating — database password, API key, TLS cert? Which backend? - audit:
Cluster name and namespace scope. Any specific concern — Git scan, SA tokens, ESO health?
Mode: design
Triggers: which pattern, ESO vs Sealed Secrets, choose secrets strategy, what should I use
Read references/secrets.md before responding.
Decision matrix
| Pattern | Best for | Tradeoff |
|---|---|---|
| External Secrets Operator (ESO) | Cloud-native backends: AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, HashiCorp Vault | Runtime dependency on provider; requires workload identity or static credentials |
| Sealed Secrets | Air-gapped or GitOps-first teams; no external runtime dependency | Rotation requires re-sealing and a Git commit; master key backup is critical |
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 · 485 lines · 31 tokens per session scan A f2704303eb98
secrets is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed 5d ago), licensed Apache-2.0. It adds 31 tokens to every session and 4,256 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
nyann:gen-devcontainer
Scaffold a .devcontainer/devcontainer.json keyed to the project's primary language. Preview-by-default; idempotent on apply (refuses to overwrite a diverged config without --force-overwrite).
conjure-config
Set, view, or remove conjure preferences. Asks questions to understand what you want, then writes plain-language instructions that conjure commands follow automatically.
conjure-agent
Creates or updates a Claude Code agent definition (/.claude/agents/ .md or project-local).
conjure
Use when you want to build a new Claude Code skill, agent, hook, or MCP server but aren't sure which — or when you want to describe what you want in plain language. Auto-detects the right artifact type, asks targeted questions, explains the reasoning, then builds it.
conjure-mcp
Create a Claude Code MCP (Model Context Protocol) server. Provide a description of what external system or data source you want Claude to connect to.
conjure-help
Show help for the conjure toolkit — all commands, argument syntax, update modes, and decision guide. Use when you want to know which conjure command to use or how any conjure command works.