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 GktuOktay/ai-skills --skill secret-scannergit clone --depth 1 https://github.com/GktuOktay/ai-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/gktuoktay/ai-skills/secret-scanner)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/secret-scanner"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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/skills/gktuoktay/ai-skills/secret-scanner"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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.00058 | $0.00673 |
| Opus 5.5 | $0.00023 | $0.00269 |
| Sonnet 5.5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
Secret Scanning and 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secret Scanning and Management
Overview
This skill focuses on detecting, managing, and preventing the leakage of sensitive information such as API keys, passwords, tokens, and certificates within the codebase and version control history.
Core Principles
1. No Hardcoded Secrets
Source code should never contain sensitive data.
- Separation of code and config: Store configuration (including secrets) in the environment, separate from the application code (as per 12-Factor App principles).
- Environment Variables: Use
.envfiles for local development but ensure they are strictly ignored in version control (.gitignore).
2. Secret Scanning
Actively scan the repository for accidentally committed secrets.
- CI/CD Integration: Integrate tools like TruffleHog, Gitleaks, or GitHub Advanced Security into your CI pipeline to scan commits before they are merged.
- Historical Scanning: Scan the entire git history, not just the current state of the code, because deleted secrets in previous commits are still compromised.
3. Pre-commit Hooks
Prevent secrets from ever entering the git history.
- Client-side checks: Set up tools like
pre-committo run secret scanners locally before a developer can successfully commit code.
4. Secret Managers
Use dedicated systems to store and inject secrets at runtime.
- Centralized Management: Use solutions like AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, or Google Secret Manager.
- Dynamic Secrets: Where possible, prefer short-lived, dynamically generated credentials over long-lived static keys.
5. Remediation
If a secret is leaked, it must be considered compromised immediately.
- Revoke and Rotate: Never just delete the secret from the code. You must revoke the leaked key at the provider and generate a new one.
Code Examples
Setting up a Pre-commit Hook for Gitleaks
Create a .pre-commit-config.yaml in your repository root:
repos:
- repo: https://github.com/zricethezav/gitleaks
rev: v8.18.1
hooks:
- id: gitleaks
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.
- 1mo ago First seen · 61 lines · 58 tokens per session scan A aebadeaed1b3
Secret Scanning and Management is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 673 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
prompt-enhancer
TÜRKÇE AÇIKLAMA ─────────────── Bu skill, belirsiz veya eksik bir kullanıcı isteğini alır ve onu daha net, daha spesifik, daha uygulanabilir bir prompt'a dönüştürür. Agent'ın yanlış anlayarak iş yapmasını önler. "Şunu düzelt" gibi muğlak bir istek, "hangi koşulda ne bekleniyor, başarı kriteri ne" formatına çevrilir.
architecture-review
Before committing to an implementation plan, run this skill to stress-test the proposed architecture. Catches over-engineering, circular dependencies, missing failure modes, security gaps, and scalability cliffs — before any code is written. Acts as a "second eye" on the plan.
brainstorming
TÜRKÇE AÇIKLAMA ─────────────── Bu skill, bir fikir veya problemi Sokratik yöntemle rafine eder. Agent sana cevap vermez — sorular sorar. Bu sorular aracılığıyla fikrin netleşir, varsayımlar sorgulanır, kapsam belirlenir ve gerçek ihtiyaç ortaya çıkar. "Ne yapalım?" sorusunu "Tam olarak ne yapmamız gerekiyor ve…
code-review
Systematic code review skill covering both requesting a review (pre-commit checklist) and receiving and responding to review feedback. Checks code quality, security, test coverage, architectural alignment, and documentation before any code is committed.
dependency-audit
Periodically scan project dependencies for security vulnerabilities, outdated packages, and unused dependencies. Produces a prioritized action report. Run before every major release and at least once per month.