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 jamditis/claude-skills-journalism --skill private-secret-scanninggit clone --depth 1 https://github.com/jamditis/claude-skills-journalismWrote 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/jamditis/claude-skills-journalism/private-secret-scanning)<a href="https://agentmods.dev/skills/jamditis/claude-skills-journalism/private-secret-scanning"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/private-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/jamditis/claude-skills-journalism/private-secret-scanning"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/private-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.00040 | $0.01721 |
| Opus 5.5 | $0.00016 | $0.00688 |
| Sonnet 5.5 | $0.00008 | $0.00344 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
private-secret-scanning scanned grade A with 1 finding 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 18d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Everything runs through one script that ships with this skill: `scripts/secret-scan.sh`. It needs only Bash (3.2 or later, so the macOS default works), git, curl, and python3. How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Private secret scanning
GitHub push protection and secret scanning are free on public repositories. Private repositories need a paid GitHub Secret Protection license. This skill gives private and shared repositories a deterministic local replacement: a pinned Gitleaks binary, three scan scopes, and git hooks that stop a leak before it leaves the machine.
Everything runs through one script that ships with this skill: scripts/secret-scan.sh. It needs only Bash (3.2 or later, so the macOS default works), git, curl, and python3.
Quick start
SCAN=path/to/private-secret-scanning/scripts/secret-scan.sh
"$SCAN" install # pinned Gitleaks 8.30.1, SHA-256 checked before install
"$SCAN" self-test # proves leaks fail and clean repos pass on this machine
cd your-repo
"$SCAN" history --report /tmp/secret-report.json # one-time audit of every commit
"$SCAN" install-hooks # pre-commit and pre-push protection from now on
Scan scopes
| Command | Scans | Use it |
|---|---|---|
staged |
the staged diff only | pre-commit hook; fastest |
push [RANGE] |
commits in RANGE, or the commits a git push is about to send (read from pre-push stdin). A new branch or tag is scanned through its full history |
pre-push hook; catches commits made with --no-verify |
history |
every commit reachable from any ref, including files deleted later | first adoption, and before a private repo goes public |
A secret that was committed and then deleted is still in history. Only history finds it, and only rotating the credential fixes it. Rewriting history does not undo a clone that already happened.
Exit codes and failure behavior
| Exit | Meaning |
|---|---|
| 0 | no leaks |
| 1 | leaks found; each is listed on stderr |
| 2 | scanner or configuration error |
The script fails closed. It exits 2, never 0, when:
- Gitleaks is missing, cannot run, or is not the pinned version.
SECRET_SCAN_CONFIGnames a file that does not exist.- Gitleaks exits with anything other than 0 or the script's own leak code. Gitleaks also exits 1 on fatal errors, such as a malformed
.gitleaks.toml, so 1 from Gitleaks is treated as an error. - The Gitleaks exit code and its report disagree, or the report is not a list of findings.
- A
.gitleaks.tomlneither extends the built-in rules nor defines its own (see below). - A hook scan finds
.gitleaks.tomlor.gitleaksignoreuntracked or changed but not committed (staged is enough forstaged). - A push sends a ref that points at something other than a commit, such as a tag on a blob. Such a ref cannot be scanned as history.
- The report cannot be read.
What ships with it
2 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.
- 18d ago First seen · 115 lines · 40 tokens per session scan A 55c6c1e4680c
private-secret-scanning is a skill published in the GitHub repository jamditis/claude-skills-journalism (423 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,721 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-29.
Other skills, from other repositories
pr-squash-message
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario…
commit
Commit the current work — runs the quality, consistency and passport gates, branches off main if needed, stages specific files, and writes a commit whose subject states what is now true. Pushes and opens a pull request only with --pr or when the user asks; never merges — a merge happens only when the user explicitly…
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…