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 bregman-arie/devops-sre-skills --skill triage-suspected-secret-exposuregit clone --depth 1 https://github.com/bregman-arie/devops-sre-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/skills/bregman-arie/devops-sre-skills/triage-suspected-secret-exposure)<a href="https://agentmods.dev/skills/bregman-arie/devops-sre-skills/triage-suspected-secret-exposure"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/triage-suspected-secret-exposure/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/bregman-arie/devops-sre-skills/triage-suspected-secret-exposure"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/triage-suspected-secret-exposure.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.00022 | $0.00458 |
| Opus 5 | $0.00011 | $0.00229 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
Triage Suspected Secret Exposure 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 13d 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.
What it actually says
When to use
Use when a secret may have been exposed (committed to VCS, printed in logs, pasted to a ticket).
Preconditions
- You have a security contact path and access to rotate the secret.
Procedure
- Treat as real until proven otherwise; minimize sharing of the secret.
- Identify what secret it is, where it was exposed, and potential access scope.
- Contain: revoke/disable the credential if supported.
- Rotate: issue a new secret, deploy it, then remove the old one.
- Remove exposure sources (redact logs, remove from docs, invalidate caches).
- Audit usage for suspicious activity.
Decision points
- Public exposure (public repo, public paste): rotate immediately.
- High-privilege secret: prioritize containment and audit.
- Cannot rotate quickly: restrict permissions and add compensating controls.
Verification
- Old credential is invalid and cannot authenticate.
- New credential works in production.
- No further leak sources remain.
Rollback / undo
- If rotation breaks service, restore from a secure rollback mechanism while keeping the old credential revoked if possible.
Escalation
- Escalate to security team for incident handling and external notifications.
- Escalate to compliance/legal if required.
Examples
Do not paste the secret into issues, PRs, or chat logs.
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.
- 13d ago First seen · 68 lines · 22 tokens per session scan A aaea22e03707
Triage Suspected Secret Exposure is a skill published in the GitHub repository bregman-arie/devops-sre-skills (22 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 458 once invoked, about $0.0001 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.
Other skills, from other repositories
incident-response
Incident triage, cascade prevention, and postmortem methodology. Use when handling production incidents, designing resilience patterns, or conducting chaos engineering exercises.
pager-triage
AI-powered incident triage for PagerDuty. List active incidents, deep-dive with timeline and alert correlation, check on-call schedules, acknowledge, resolve, and annotate — all from your agent. Read-only by default; write operations require explicit --confirm.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
deck-safety-alert
A slide-deck template for security warnings, risk reviews, incident retrospectives, red-team work, and policy-as-code. It uses warning stripes, alert colours, risk tiers, checklists, charts, and highlighted policy examples.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…