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 cboone/agent-harness-plugins --skill set-up-secret-scanninggit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWrote 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/cboone/agent-harness-plugins/set-up-secret-scanning)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/set-up-secret-scanning"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/set-up-secret-scanning/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/cboone/agent-harness-plugins/set-up-secret-scanning"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/set-up-secret-scanning.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.00046 | $0.01055 |
| Opus 5.5 | $0.00018 | $0.00422 |
| Sonnet 5.5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
set-up-secret-scanning 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 26d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set-Up Secret Scanning
Set up secret scanning in a repository with gitleaks and TruffleHog GitHub Actions workflows and optional .gitleaks.toml configuration.
The two tools are complementary:
- Gitleaks performs fast pattern matching.
- TruffleHog performs deeper verification-based scanning that confirms whether detected credentials are still live.
Both run on pushes to main, on every pull request, and on manual workflow_dispatch.
Workflow
1. Check for Existing Setup
Look for existing secret scanning workflows and configuration:
ls .github/workflows/gitleaks.yml
ls .github/workflows/gitleaks.yaml
ls .github/workflows/trufflehog.yml
ls .github/workflows/trufflehog.yaml
Also check for an existing .gitleaks.toml:
ls .gitleaks.toml
If any workflows already exist, inform the user and ask whether to overwrite each one or skip it.
2. Choose Scanning Tools
If the user specified a tool selection in their request (gitleaks, trufflehog, or both), use it directly instead of asking.
Ask the user which tools to set up:
- Both gitleaks and TruffleHog (recommended): complementary coverage with fast pattern matching and deep verification
- Gitleaks only: fast pattern matching on every push and PR
- TruffleHog only: verification-based scanning on pushes to main
3. Generate Gitleaks Workflow
If gitleaks was selected, read ./references/gitleaks-workflow.md for the workflow template and create .github/workflows/gitleaks.yml from it.
Write the file using the Write tool. The .github/workflows/ directory will be created automatically if it does not exist.
4. Generate TruffleHog Workflow
If TruffleHog was selected, read ./references/trufflehog-workflow.md for the workflow template and create .github/workflows/trufflehog.yml from it.
Write the file using the Write tool.
5. Optionally Generate Gitleaks Configuration
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 26d ago Changed · -6 lines · -79 tokens per session fced5f14f837
- 1mo ago First seen · 111 lines · 125 tokens per session scan A c96e2a862e2e
set-up-secret-scanning is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,055 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-09-03.
Other skills, from other repositories
skillshare-app-release
A release workflow for shipping the skillshare desktop application on macOS, Windows, and Linux. It coordinates the release pull request, automated builds, GitHub release, updater feed, and Homebrew package.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions).
devops
CI/CD, container orchestration, cloud architecture, monitoring, infrastructure security, and platform automation skills. Docker, Kubernetes, Terraform, GitHub Actions. Triggers on: CI/CD, Docker, Kubernetes, Terraform, deploy, monitoring, infra, GitOps, observability, SRE.