secrets-management

secrets-management is a skill for Claude Code, Codex from aiming-lab/MetaClaw. It costs 55 tokens per session (236 once invoked), scanned A, original, MIT.

Guidelines for handling API keys, passwords, tokens, private keys, and other credentials used by software. They recommend keeping secrets out of source code, logs, and committed configuration files.

In plain words
What is it for?
Use it when adding authentication, configuring credentials, reviewing code for exposed secrets, setting up .gitignore, or responding to a leaked key or token.
Why use it?
It reduces the risk of credentials being exposed in a code repository or application output. It also covers environment variables, production secrets managers, scanning, and rotation after leaks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when adding authentication, configuring credentials, reviewing code for exposed secrets, setting up .gitignore, or responding to a leaked key or token.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aiming-lab/metaclaw/secrets-management
About the project

MetaClaw is an AI-agent system that learns from conversations and evolves its behavior over time. It provides memory and learning modes for users who want an agent that adapts across interactions, with support for multiple claw-based agent projects.

aiming-lab/MetaClaw · 3,495 stars · on GitHub · arxiv.org

Install

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.

Any agent
npx skills add aiming-lab/MetaClaw --skill secrets-management
Clone the repo
git clone --depth 1 https://github.com/aiming-lab/MetaClaw

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for secrets-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/aiming-lab/metaclaw/secrets-management/github.svg)](https://agentmods.dev/skills/aiming-lab/metaclaw/secrets-management)
Your own site
<a href="https://agentmods.dev/skills/aiming-lab/metaclaw/secrets-management"><img src="https://agentmods.dev/badge/skills/aiming-lab/metaclaw/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.

agentmods 80×15 button for secrets-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/aiming-lab/metaclaw/secrets-management"><img src="https://agentmods.dev/badge/skills/aiming-lab/metaclaw/secrets-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00236
Opus 5 $0.00028 $0.00118
Sonnet 5 $0.00011 $0.00047
Haiku 4.5 $0.00006 $0.00024

Measured 9d ago against content hash 31022f24b891, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 9d 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.

memory_data/skills/secrets-management/SKILL.md · 21 lines

What it actually says

Secrets Management

Rules:

  1. Never hardcode secrets in source files, configs committed to git, or logs.
  2. Use environment variables for local development (python-dotenv).
  3. Use a secrets manager (AWS Secrets Manager, HashiCorp Vault, 1Password CLI) in production.
  4. Add .env and *.pem to .gitignore before the first commit.
  5. Rotate secrets immediately if they are exposed (leaked in a commit, log, or error message).

Scanning: Use ggshield, truffleHog, or git-secrets in CI to block secret commits.

Anti-patterns:

  • os.environ.get('KEY', 'hardcoded_default') in production code.
  • Logging full request/response bodies that may contain tokens.
Changes

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.

  1. 9d ago First seen · 21 lines · 55 tokens per session scan A 31022f24b891

Subscribe to this mod's changes

secrets-management is a skill published in the GitHub repository aiming-lab/MetaClaw (3,495 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 236 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

llama-factory

Expert guidance for fine-tuning LLMs with LLaMA-Factory - WebUI no-code, 100+ models, 2/3/4/5/6/8-bit QLoRA, multimodal support.

davila7/claude-code-templates · 51 tokens

tinker-fine-tuning

Provides guidance for fine-tuning LLMs using the Tinker cloud training API from Thinking Machines Lab. Use when running supervised fine-tuning, reinforcement learning (GRPO/PPO), or LoRA training on cloud GPUs via Tinker's managed infrastructure instead of local compute.

synthetic-sciences/openscience · 62 tokens

tinker-training-cost

Calculates training costs for Tinker fine-tuning jobs. Use when estimating costs for Tinker LLM training, counting tokens in datasets, or comparing Tinker model training prices. Tokenizes datasets using the correct model tokenizer and provides accurate cost estimates.

synthetic-sciences/openscience · 55 tokens

transformers

This skill should be used when working with pre-trained transformer models for natural language processing, computer vision, audio, or multimodal tasks. Use for text generation, classification, question answering, translation, summarization, image classification, object detection, speech recognition, and fine-tuning…

synthetic-sciences/openscience · 63 tokens

colab-finetuning

Fine-tune LLMs on Google Colab GPUs directly from openscience. Connects to Colab runtimes via WebSocket bridge for remote training with Unsloth. Supports SFT, GRPO, DPO, vision, and TTS workflows on free T4 to Pro A100 GPUs.

synthetic-sciences/openscience · 67 tokens

llm-integration

LLM integration patterns for function calling, streaming responses, local inference with Ollama, and fine-tuning customization. Use when implementing tool use, SSE streaming, local model deployment, LoRA/QLoRA fine-tuning, or multi-provider LLM APIs.

yonatangross/orchestkit · 58 tokens