ZCF is a command-line setup tool for configuring Claude Code and Codex with agents, instructions, skills, hooks, commands, and settings. It is for developers who want to install and personalize these coding-agent workflows through an interactive setup.
Borrowing it
Nothing to install: this file belongs to UfoMiao/zcf. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/UfoMiao/zcf/main/.claude/skills/zcf-pr/SKILL.mdgit clone --depth 1 https://github.com/UfoMiao/zcfWrote 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/ufomiao/zcf/zcf-pr)<a href="https://agentmods.dev/skills/ufomiao/zcf/zcf-pr"><img src="https://agentmods.dev/badge/skills/ufomiao/zcf/zcf-pr/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/ufomiao/zcf/zcf-pr"><img src="https://agentmods.dev/badge/skills/ufomiao/zcf/zcf-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00523 |
| Opus 5.5 | $0.00008 | $0.00209 |
| Sonnet 5.5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
zcf-pr 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 2d 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.
What it actually says
ZCF PR
Open a pull request for the current branch.
Usage: /zcf-pr [--base <branch>] [--draft] [--title <title>] (base defaults to main). Arguments: $ARGUMENTS
Steps
- Preconditions. Stop with a one-line explanation if the current branch is the base branch, or if there are no commits ahead of the base. If there are uncommitted changes, list them and ask whether to commit them (stage by name, never
git add .) or leave them out. - Understand the change. Read
git log <base>..HEADandgit diff <base>...HEAD. Classify it from the diff itself, not from keywords in commit messages. - Verify proportionally. Unless this session already ran them on the current HEAD, run the checks that
AGENTS.mdcalls for on the changed paths: the "Check with" column of its trigger table, pluspnpm typecheckandpnpm test:run(about 60 s together) when source files changed. Docs-only branches need no tests. Report failures to the user instead of opening the PR. - Title. Use
--titleif given; otherwise a Conventional Commits title (at most 100 characters) that summarizes the whole branch, not just its first commit. - Body. Fill in
.github/PULL_REQUEST_TEMPLATE:- Description: what changed and why, in a few sentences. Link related issues.
- Type of Change: tick what the diff shows. Breaking change only if CLI flags, defaults or written config change incompatibly.
- Testing and Checklist: tick only what actually happened in this session, such as tests you ran or added. Leave the rest unticked rather than guessing.
- Mention anything not verified (for example Windows behavior).
- Push and create.
git push -u origin <branch>, thengh pr create --base <base> --title ... --body-file <tmpfile>(add--draftif requested). Delete the temp file afterwards and print the PR URL.
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.
- 2d ago Changed · -429 lines · +9 tokens per session 232e102287a5
- 1mo ago First seen · 455 lines · 12 tokens per session scan A 7e9e04d0bf16
zcf-pr is a skill published in the GitHub repository UfoMiao/zcf (6,079 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 523 once invoked, about $0.0001 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-30.
Other skills, from other repositories
cli-forge-github
Audit and fix GitHub repository health: rulesets vs CI alignment, branch hygiene, PR lifecycle, release automation flow, permission issues, and transient CI failures. Detects misconfigurations that cause PRs to hang, CI to fail silently, branches to accumulate, and releases to stall. Use when the user says 'PR stuck'…
cli-git-conventional
Enforce Conventional Commits v1.0.0, SemVer 2.0.0, branch naming, commit guard, full-directory AI marker audits, and human ghostwriter style on all git/jj operations. Zero AI markers. Use on 'commit', 'branch', 'tag', 'release', 'changelog', 'semver', 'bump version', 'next version', 'CHANGELOG.md', 'audit markers'…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.