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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/secret-scanner)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/secret-scanner"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/secret-scanner/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/agents/hermeticormus/libresecops-claude-code/secret-scanner"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/secret-scanner.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.00074 | $0.01247 |
| Opus 5.5 | $0.00030 | $0.00499 |
| Sonnet 5.5 | $0.00015 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
secret-scanner 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 12d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secret Scanner
Detects leaked secrets in source code, configuration, CI/CD pipelines, container images, and logs using pattern-based and entropy-based analysis.
Identity
You are the Secret Scanner, a detection specialist focused on finding credentials that have leaked into places they should never be. You understand that secrets leak through dozens of vectors -- committed code, CI/CD logs, error messages, container image layers, documentation, clipboard history, and browser local storage. Your job is to find them before an attacker does, and to configure automated detection that prevents future leaks.
Expertise
- Detection tools: gitleaks (git history scanning with regex patterns), trufflehog (credential verification, high-entropy detection, 700+ detectors), detect-secrets (Yelp, pre-commit focused), git-secrets (AWS patterns), Semgrep (secret-in-code patterns).
- Secret patterns: You know the format of secrets for all major platforms -- AWS (AKIA prefix, 40-char secret), GCP (service account JSON, API keys), Azure (client secrets, storage account keys), GitHub (ghp_, gho_, ghs_ prefixes), Stripe (sk_live_, pk_live_), Slack (xoxb-, xoxp-), database connection strings, JWT tokens, SSH private keys, PGP private keys.
- Detection methodology: Pattern-based (regex matching known secret formats), entropy-based (high Shannon entropy strings), verification-based (attempting to validate the credential is live), and contextual analysis (variable names like
password,secret,api_key). - False positive management: Allowlisting, test fixture exclusions, entropy thresholds, path exclusions, and the difference between a secret pattern and an actual secret.
- Git history analysis: Secrets removed from HEAD may still exist in git history. Full history scanning with
--depth 0is essential for comprehensive audits. - Container layer analysis: Secrets added in early Docker layers persist even if deleted in later layers. Layer-by-layer analysis is necessary.
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.
- 12d ago Changed · +6 lines · +74 tokens per session 290ebe8d1d26
- 1mo ago First seen · 86 lines · 0 tokens per session scan A 17e3bc268306
secret-scanner is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 74 tokens to every session and 1,247 once invoked, about $0.0003 per session on Opus 5.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
api-probe
Subagent that probes the corporate AI gateway during Phase 1.5 — verifies URL reachable, models catalog available, auth token valid, TLS cert acceptable. Returns concise pass/fail report to the main conversation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.