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 skills/evolplus/talos/secrets-config-auditnpx skills add evolplus/talos --skill secrets-config-auditgit clone --depth 1 https://github.com/evolplus/talosWrote 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/evolplus/talos/secrets-config-audit)<a href="https://agentmods.dev/skills/evolplus/talos/secrets-config-audit"><img src="https://agentmods.dev/badge/skills/evolplus/talos/secrets-config-audit.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.00056 | $0.00670 |
| Opus 5 | $0.00028 | $0.00335 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade B, and why
secrets-config-audit 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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- Never run commands that dump credential material, including full `docker compose config`, `kubectl config view --raw`, `env`, or `printenv` on remote hosts. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets Config Audit
When to use
Use this skill before any deployment that depends on runtime configuration, secrets, environment files, registry credentials, cloud credentials, SSH, Kubernetes, or external service keys.
Inputs and outputs
- Inputs: SRS environment contract, architecture config section, safe env templates, deploy mechanism, secret manager references, target environment, and required service integrations.
- Outputs: redacted config readiness verdict, missing key names, unsafe storage findings, rotation/owner notes, and deploy-report config fields.
Procedure
- Collect declared keys. Read SRS/architecture config contracts and safe templates (
.env.example,.env.template,.env.sample) for key names, owners, required environments, and secret classification. - Detect secret-bearing files by status only. Check presence/path of
.env*,.ssh/,.k8s/*config*,.docker/config.json, kubeconfigs, and credential files without reading contents. - Verify injection path. Confirm each secret has a source: secret manager, Kubernetes Secret/ExternalSecret, CI/CD variable, operator-managed env file, or documented runtime injection.
- Check non-secret config. Verify public endpoints, feature flags, regions, log levels, and build/runtime config are represented in templates and deployment manifests.
- Look for unsafe patterns. Flag secrets in committed manifests, plain values in docs, full
docker compose configoutput, kubeconfig dumps, copied.env, or hardcoded credentials. - Assess rotation/ownership. Record owner and rotation expectation by secret name or category only. Do not ask the model to inspect values or token ages unless metadata is available without secrets.
- Emit verdict.
pass,pass-with-warnings, orblocked.
Hard rules
- Never read, print, copy, summarize, or diff secret values.
- Never run commands that dump credential material, including full
docker compose config,kubectl config view --raw,env, orprintenvon remote hosts. - Never create
.env*or credential files for the operator. - Never mark config ready when required key names are missing from templates/contracts or injection paths are unknown.
- Never place secret values in deploy reports; use key names and status only.
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 · 45 lines · 56 tokens per session scan B 989ac7388092
secrets-config-audit is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 670 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…