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 valtterimelkko/agent-workflow-skills --skill secret-scanninggit clone --depth 1 https://github.com/valtterimelkko/agent-workflow-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/valtterimelkko/agent-workflow-skills/secret-scanning)<a href="https://agentmods.dev/skills/valtterimelkko/agent-workflow-skills/secret-scanning"><img src="https://agentmods.dev/badge/skills/valtterimelkko/agent-workflow-skills/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/valtterimelkko/agent-workflow-skills/secret-scanning"><img src="https://agentmods.dev/badge/skills/valtterimelkko/agent-workflow-skills/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.00131 | $0.01412 |
| Opus 5.5 | $0.00052 | $0.00565 |
| Sonnet 5.5 | $0.00026 | $0.00282 |
| Haiku 4.5 | $0.00013 | $0.00141 |
Grade C, and why
secret-scanning scanned grade C with 2 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 24d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
tar xzf gl.tgz gitleaks && install -m 0755 gitleaks /usr/local/bin/gitleaks; cd /; rm -rf "$D" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSfL -o gl.tgz "https://github.com/gitleaks/gitleaks/releases/download/v$V/gitleaks_${V}_linux_x64.tar.gz" How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secret scanning
The goal is to keep credentials out of repositories. Scanning is the check; the design rule comes first:
Credentials live outside the repo tree. Code reads them from paths or environment variables that point outside the repository (for example
~/.pi-web-ui/internal-api-token), and should refuse a credential path that resolves inside its own repo..gitignoreis only a backstop: onegit add -for one renamed file defeats it.
The tool: gitleaks
gitleaks is a single binary and needs no account or human step. Check it with
gitleaks version. If it is missing, install a pinned release and verify the checksum:
V=8.30.1; D=$(mktemp -d); cd "$D"
curl -sSfL -o gl.tgz "https://github.com/gitleaks/gitleaks/releases/download/v$V/gitleaks_${V}_linux_x64.tar.gz"
curl -sSfL -o sums.txt "https://github.com/gitleaks/gitleaks/releases/download/v$V/gitleaks_${V}_checksums.txt"
grep "gitleaks_${V}_linux_x64.tar.gz" sums.txt | sed "s/gitleaks_${V}_linux_x64.tar.gz/gl.tgz/" | sha256sum -c -
tar xzf gl.tgz gitleaks && install -m 0755 gitleaks /usr/local/bin/gitleaks; cd /; rm -rf "$D"
Never print a secret
Always pass --redact. Never print, paste, quote or store a matched value,
including in reports, commit messages, chat or evidence files. Not even partly, and
not "masked in context". Triage from metadata only: rule id, file, line, commit,
the key name that matched, and whether the file still exists at HEAD. On some hosts
the agent's permission layer blocks commands that would expose credential values.
Treat that block as correct; do not work around it.
Commands
| Need | Command |
|---|---|
| Full history of a repo (before publishing; public-repo audit) | gitleaks git --redact -v <repo> |
| Working tree or any directory (evidence before copying it into a repo) | gitleaks dir --redact -v <path> |
| Only unpushed commits | gitleaks git --redact --log-opts="origin/main..HEAD" <repo> |
| Staged changes (pre-commit) | gitleaks git --pre-commit --staged --redact -v |
| Machine-readable triage | add --report-format json --report-path /tmp/gl.json (the report is redacted too; delete it afterwards) |
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.
- 24d ago First seen · 112 lines · 131 tokens per session scan C 663813f708fd
secret-scanning is a skill published in the GitHub repository valtterimelkko/agent-workflow-skills (2 stars, last pushed 21d ago), licensed MIT. It adds 131 tokens to every session and 1,412 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.