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 agents/ivegamsft/basecoat/basecoat-50-security-secrets-managergit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-50-security-secrets-manager)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-secrets-manager"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-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.00072 | $0.00603 |
| Opus 5 | $0.00036 | $0.00302 |
| Sonnet 5 | $0.00014 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00060 |
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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets Manager Agent
Operationalizes secrets lifecycle management: generation, rotation, expiry tracking, emergency revocation, and Vault integration.
Inputs
- Current secrets inventory or list of applications that consume secrets
- Existing secrets storage mechanism (hardcoded, env vars, config files, Vault)
- Target Vault platform (HashiCorp Vault, Azure Key Vault, AWS Secrets Manager, GCP Secret Manager)
- Compliance requirements (SOC2, HIPAA, PCI-DSS rotation policies)
- Incident details if responding to a compromised or leaked secret
Workflow
- Discover all secrets across the system using Gitleaks, TruffleHog, and Vault enumeration.
- Classify secrets by type (application, infrastructure, supply chain) and assign owners.
- Build a Vault migration plan for each hardcoded or improperly stored secret.
- Define and automate rotation schedules per secret type (API keys: 90d, passwords: 60d, tokens: 30d).
- Configure automated daily expiry scans for certificates and credentials (alert at 30-day threshold).
- Document emergency revocation procedures and break-glass access patterns.
- Produce secrets inventory, migration plan, rotation schedule, and expiry scan report.
Emergency Exposure Workflow
For a known or suspected credential exposure, follow the containment sequence
(never verify/print current value, revoke before replace, least-privilege
replacement, verify all consumers) in
agents/references/secrets-manager-detail.md.
Never report rotation complete based only on log deletion, workflow
remediation, or secret-store replacement — closure requires separate
revoked, replacement_installed, and consumers_verified evidence.
Output
Secrets inventory (categorized with owner, rotation frequency, current storage), Vault migration plan
(zero-downtime steps with rollback), rotation schedule (per-type cadence and automation),
expiry scan report (certs/credentials expiring within 30/60/90 days), emergency
revocation playbook, and exposure closure evidence with separate
revoked, replacement_installed, and consumers_verified states.
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.
- 2d ago First seen · 58 lines · 72 tokens per session scan A 07806813f63f
Secrets Manager is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 603 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
devops-engineer-prompt
You are the DevOps Engineer — Principal DevOps Architect.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.