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 agentmods add instructions/ufomiao/zcf/agents-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/instructions/ufomiao/zcf/agents-md)<a href="https://agentmods.dev/instructions/ufomiao/zcf/agents-md"><img src="https://agentmods.dev/badge/instructions/ufomiao/zcf/agents-md.svg" alt="Measured on agentmods" 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 | $0.00633 | $0.00633 |
| Opus 5 | $0.00316 | $0.00316 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
zcf AGENTS.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Source code lives in src/, with the CLI entry point in src/cli.ts and features split into commands/, config/, utils/, and types/. Shared assets (banners, locale files, templates) are under src/assets/, src/i18n/, and top-level templates/. Generated bundles reside in dist/; avoid editing them directly. Tests mirror the runtime tree inside tests/ (unit/, integration/, and helper fixtures), and documentation resides in docs/ plus localized READMEs.
Build, Test, and Development Commands
pnpm install— sync dependencies defined by the workspace catalogs.pnpm dev— run the CLI in watch mode viatsxfor rapid iteration.pnpm build— produce the distributable withunbuild.pnpm typecheck— validate TypeScript types without emitting files.pnpm lint/pnpm lint:fix— run ESLint with the shared @antfu config.pnpm test/pnpm test:run— execute Vitest suites; add:coveragefor V8 coverage reports.
Coding Style & Naming Conventions
Stick to TypeScript ESM modules with 2-space indentation and single quotes, matching the existing files. Use camelCase for functions and variables, PascalCase for types and classes, and kebab-case for new filenames in CLI modules. Prefer named exports from feature modules and keep side effects in entry points only. ESLint (via eslint.config.ts) and lint-staged enforce formatting—run them locally before pushing.
Testing Guidelines
Vitest powers both unit and integration coverage. Place fast, isolated checks in tests/unit/*.test.ts and cross-module flows in tests/integration/. Reuse helpers from tests/helpers/ and fixtures in tests/fixtures/ to reduce duplication. When adding tests, assert CLI behavior via snapshot-safe strings and ensure pnpm test:coverage stays above existing thresholds (current reports live in coverage/).
Commit & Pull Request Guidelines
Commits follow Conventional Commits (feat:, fix:, etc.) with ≤100-character subject lines; scopes are optional but descriptive scopes (for example feat(config): ...) help reviewers. Start bodies with a blank line when explaining rationale. For pull requests, include a succinct summary, reproduction or validation steps (e.g., pnpm test output), any screenshots of CLI prompts when UX changes, and link related issues or changesets. Ensure the branch passes lint, typecheck, and tests before requesting review.
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.
- 4d ago First seen · 25 lines · 633 tokens per session scan A 8e95d6955969
zcf AGENTS.md is an instructions file published in the GitHub repository UfoMiao/zcf (6,085 stars, last pushed 3d ago), licensed MIT. It adds 633 tokens to every session, about $0.0032 per session on Opus 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 instructions, from other repositories
SeekMoney-ai CLAUDE.md
Instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
claude-sessions CLAUDE.md
Instructions for gapmiss/claude-sessions, covering claude sessions — obsidian plugin, development, file structure, code exploration (cymbal) and conventions.
delphi-spec-kit AGENTS.md
Instructions for delphicleancode/delphi-spec-kit, covering delphi ai spec-kit — agents.md, language and stack, naming conventions — pascal guide, general rule and mandatory prefixes.
embedded-systems-architect AGENTS.md
Instructions for Zachariah9420/embedded-systems-architect: This repository ships an agent skill for embedded-systems and edge-AI development work.
contexture AGENTS.md
AGENTS.md instructions for AcKeskin/contexture, covering agents.md, stance (how to engage), commands, testing and project structure.