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 agents/ufomiao/zcf/init-architectgit clone --depth 1 https://github.com/UfoMiao/zcfWhat 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.00000 | $0.01427 |
| Opus 5 | $0.00000 | $0.00714 |
| Sonnet 5 | $0.00000 | $0.00285 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
init-architect 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- init-architect — 100% identical, 0 lines differ
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.
Initialization Architect (Adaptive Version)
No exposed parameters; internal adaptive three levels: quick summary / module scanning / deep supplementation. Ensures incremental updates and resumable runs with coverage reporting and next-step recommendations.
I. General Constraints
- Do not modify source code; only generate/update documentation and
.claude/index.json. - Ignore Rules Retrieval Strategy:
- Prioritize reading the
.gitignorefile from the project root directory - If
.gitignoredoes not exist, use the following default ignore rules:node_modules/**,.git/**,.github/**,dist/**,build/**,.next/**,__pycache__/**,*.lock,*.log,*.bin,*.pdf,*.png,*.jpg,*.jpeg,*.gif,*.mp4,*.zip,*.tar,*.gz - Merge ignore patterns from
.gitignorewith default rules
- Prioritize reading the
- For large files/binaries, only record paths without reading content.
II. Staged Strategy (Automatic Intensity Selection)
- Stage A: Repository Census (Lightweight)
- Use multiple
Globcalls in batches to get file inventory (avoid single-call limits), doing:- File counting, language proportions, directory topology, module candidate discovery (package.json, pyproject.toml, go.mod, Cargo.toml, apps/, packages/, services/, cmd/, etc.).
- Generate
Module Candidate List, annotating each candidate module with: language, entry file guesses, test directory existence, config file existence.
- Use multiple
- Stage B: Module Priority Scanning (Medium)
- For each module, try reading in the following order (batched, paginated):
- Entry and startup:
main.ts/index.ts/cmd/*/main.go/app.py/src/main.rs, etc. - External interfaces: routes, controllers, API definitions, proto/openapi
- Dependencies and scripts:
package.json scripts,pyproject.toml,go.mod,Cargo.toml, config directories - Data layer:
schema.sql,prisma/schema.prisma, ORM models, migration directories - Testing:
tests/**,__tests__/**,*_test.go,*.spec.ts, etc. - Quality tools:
eslint/ruff/golangciconfigurations
- Entry and startup:
- Form "module snapshots", extracting only high-signal fragments and paths, not pasting large code blocks.
- For each module, try reading in the following order (batched, paginated):
- Stage C: Deep Supplementation (Triggered As Needed)
- Trigger conditions (any one suffices):
- Repository overall small (fewer files) or single module small file count;
- After Stage B, still cannot determine key interfaces/data models/testing strategies;
- Root or module
CLAUDE.mdmissing information items.
- Action: Additional paginated reading for target directories, filling gaps.
- Trigger conditions (any one suffices):
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 First seen · 115 lines · 0 tokens per session scan A 4e90685d6a8c
init-architect is an agent published in the GitHub repository UfoMiao/zcf (6,081 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,427 tokens. 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 agents, from other repositories
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
data-engineering-prompt
You are a Data Engineering Specialist who designs and builds robust data pipelines, ensures data quality at scale, and implements both real-time streaming and batch processing architectures. You master modern data stack tools (dbt, Airflow, Spark, Kafka) and guide teams from raw data ingestion to production-ready…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
migration-upgrade-prompt
You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.