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.
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 UfoMiao/zcf --skill init-projectgit 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/init-project)<a href="https://agentmods.dev/skills/ufomiao/zcf/init-project"><img src="https://agentmods.dev/badge/skills/ufomiao/zcf/init-project/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/init-project"><img src="https://agentmods.dev/badge/skills/ufomiao/zcf/init-project.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.00020 | $0.00638 |
| Opus 5.5 | $0.00008 | $0.00255 |
| Sonnet 5.5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
init-project 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ask — 88% identical, 69 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
/init-project <PROJECT_SUMMARY_OR_NAME>
Objective
Initialize project AI context using a mixed strategy of "concise at root + detailed at module level":
- Generate/update
CLAUDE.mdat repository root (high-level vision, architecture overview, module index, global standards). - Generate/update local
CLAUDE.mdin identified module directories (interfaces, dependencies, entry points, tests, key files, etc.). - ✨ For improved readability, automatically generate Mermaid structure diagrams in the root
CLAUDE.mdand add navigation breadcrumbs to each moduleCLAUDE.md.
Orchestration Instructions
Step 1: Call the get-current-datetime sub-agent to obtain the current timestamp.
Step 2: Call the init-architect sub-agent once, with input:
project_summary: $ARGUMENTScurrent_timestamp: (timestamp from step 1)
Execution Strategy (Agent adapts automatically, no user parameters needed)
- Stage A: Repository Census (Lightweight) Quickly count files and directories, identify module roots (package.json, pyproject.toml, go.mod, apps/, packages/, services/*, etc.).
- Stage B: Module Priority Scanning (Medium) For each module, perform targeted reading and sampling of "entry/interfaces/dependencies/tests/data models/quality tools".
- Stage C: Deep Supplementation (As Needed) If repository is small or module scale is small, expand reading scope; if large, perform batch supplemental scanning on high-risk/high-value paths.
- Coverage Measurement and Resumability
Output "scanned files / estimated total files, covered module ratio, ignored/skipped reasons" and list "recommended next-step deep-dive sub-paths". When running
/init-projectrepeatedly, perform incremental updates and breakpoint resumable scanning based on previous index.
Security and Boundaries
- Only read/write documentation and indexes, do not modify source code.
- Ignore common generated artifacts and binary large files by default.
- Print "summary" in main dialog, write full content to repository.
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.
- 1mo ago First seen · 55 lines · 20 tokens per session scan A 75664c525f6c
init-project is a skill published in the GitHub repository UfoMiao/zcf (6,079 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 638 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
integrations
NextDNS integration guides for third-party platforms and services. This skill should be used when integrating NextDNS with routers, home automation systems, network management platforms, or other third-party services. It also guides transport selection across DoH, DoT, DoQ, DoH3, IPv6, and legacy DNS. Triggers on…
nextdns-cli
NextDNS CLI client best practices for installation, configuration, and management of DNS-over-HTTPS proxy. This skill should be used when installing NextDNS on routers, servers, or client devices, configuring DNS settings, managing the daemon, or troubleshooting DNS issues. Triggers on tasks involving NextDNS CLI…
nextdns-ui
NextDNS Web UI configuration and management best practices. This skill should be used when configuring NextDNS profiles via the web interface (my.nextdns.io), including security features, privacy lists, parental controls, and monitoring logs.
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-watermark
Steganographic code watermarking for IP defense. Generates multi-layered fingerprints that survive AI rewrites, language changes, renaming, and clean-code passes. Produces timestamped cryptographic commitments for legal proof of authorship. Use when the user wants to watermark a codebase, protect IP, prove code…
cli-audit-tangle
Detect spaghetti code and dependency cycles using graph theory, spectral analysis, and biomimetic patterns. Finds god functions, circular dependencies, dead code, suboptimal module boundaries, CI/CD pipeline deadlocks, and inefficient call patterns. Uses call graph topology (not just line-level metrics) to identify…