scan-secrets
Blocks known credential patterns -- vendor key prefixes, private-key blocks, and key/token/password assignments -- at two enforcement points: at commit (the git hook, over staged changes) and at agent tool-use (the mcp-gateway / agent write guard, over a tool call's arguments), so a secret is caught as the agent writes it, before it ever reaches a commit. Matched by pattern, not by entropy analysis. Best-effort guard; not a replacement for a dedicated secret scanner.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- scan-secrets
- metadata
- { "chock.artifact": "hook", "chock.enforcement": "block", "chock.coverage_without_chock": "advisory" }
- description
- Blocks known credential patterns -- vendor key prefixes, private-key blocks, and key/token/password assignments -- at two enforcement points: at commit (the git hook, over staged changes) and at agent tool-use (the mcp-gateway / agent write guard, over a tool call's arguments), so a secret is caught as the agent writes it, before it ever reaches a commit. Matched by pattern, not by entropy analysis. Best-effort guard; not a replacement for a dedicated secret scanner.
03 SKILL.md 正文
Scan Secrets
Blocks known credential patterns -- vendor key prefixes, private-key blocks, and key/token/password assignments -- at two enforcement points: at commit (the git hook, over staged changes) and at agent tool-use (the mcp-gateway / agent write guard, over a tool call's arguments), so a secret is caught as the agent writes it, before it ever reaches a commit. Matched by pattern, not by entropy analysis. Best-effort guard; not a replacement for a dedicated secret scanner.
on(commit|tool_use): block(content_regex) scan=added_lines forbidden_path_regex=(\.env(\.(?!(sample|example|template|dist|def... ...
Potential secret detected in this change. Remove credentials and rotate any exposed keys. At commit, add '# pragma: allowlist secret' on the same line only for documented test fixtures; the pragma is NOT honored at tool-use, where the scanned text is a live tool argument an appended token could neutralize.
This skill is advisory: the client reading it has no mechanism to enforce it. The same policy compiled by chock becomes a git hook that exits non-zero. See https://github.com/open-coder-ai/chock
04 同仓库更多 Skills
validate
Lint Chock policy conformance. args(policy_id or all) returns(findings, verdict) invoke(validate, check, promotion_to_review) exclude(eval, optimize)
policy-init
Create conformant Chock policy from request. args(request, target_path, artifact_hint) returns(folder, wiring) invoke(skill, hook, rule, workflow, convention, always_never) exclude(coding, edit_existing)
optimize
Improve Chock policy from usage evidence. args(policy_path, >=3 traces) returns(promoted_edit / rejected_record / no_bar) invoke(misfire, ignore, tuning) exclude(policy_init, one_off_edit)
eval
Run Chock policy eval suite. args(policy_path) returns(pass_rate, verdict) invoke(test, run_evals, promotion_check) exclude(validate, optimize)
verify-dependency-exists
Block hallucinated or unknown dependencies before they enter the repo. Watches requirements.txt, pyproject.toml, package.json, and go.mod, and blocks any newly added dependency not present in the allowlist file. Opt-in: disabled by default because it requires a curated allowlist. Enable with `chock enable verify-dependency-exists` after populating .chock/dependency-allowlist.txt.
token-efficiency
trigger: large command output, broad searches, re-reading unchanged files, front-loading references. avoid: wasting context window on low-signal content.