What is project-init?

A project-onboarding command that detects a repository's technology stack and creates a dry-run plan for adding project guidance, skills, or settings to supported coding agents. Dry-run means it shows proposed changes without applying them.

Use it to inspect install manifests, map a project to its tools, and prepare a controlled onboarding plan for an agent.

It makes agent setup reviewable and helps preserve existing project instructions instead of overwriting them.

project-init — Command for Claude Code by Fmarzochi

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/Fmarzochi/EGC

agentmods

npx agentmods add commands/fmarzochi/egc/project-init

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fmarzochi/egc/project-init/github.svg)](https://agentmods.dev/commands/fmarzochi/egc/project-init)

Your own site

<a href="https://agentmods.dev/commands/fmarzochi/egc/project-init"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/project-init/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/fmarzochi/egc/project-init"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/project-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 924 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00023	$0.00924
Opus 5	$0.00012	$0.00462
Sonnet 5	$0.00005	$0.00185
Haiku 4.5	$0.00002	$0.00092

Measured 6d ago against content hash d59815d04c70, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

project-init 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 6d 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.

commands/project-init.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/project-init

Create a safe, reviewable EGC onboarding plan for the current project. This command should start in dry-run mode and only write files after explicit user approval.

Usage

/project-init
/project-init --dry-run
/project-init --target Gemini
/project-init --target cursor
/project-init --skills continuous-learning-v2,security-review
/project-init --config egc-install.json

Safety Rules

Default to dry-run. Do not modify Gemini.md, settings files, rules, skills, or install state until the user approves the concrete plan.
Preserve existing project guidance. If Gemini.md, .Gemini/settings.local.json, .cursor/, .codex/, .gemini/, .opencode/, .codebuddy/, .joycode/, or .qwen/ already exists, inspect it and propose a merge/append plan instead of overwriting.
Use EGC's installer and manifest tooling. Do not hand-copy files or clone arbitrary remotes as an install shortcut.
Keep permissions narrow. Any generated settings should match detected build/test/lint tools and avoid broad shell access.
Report exactly what would change before applying anything.

Detection Inputs

Read the current project root and detect stack signals from:

package manager files: package.json, package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lockb
language manifests: pyproject.toml, requirements.txt, go.mod, Cargo.toml, pom.xml, build.gradle, build.gradle.kts
framework files: next.config.*, vite.config.*, tailwind.config.*, Dockerfile, docker-compose.yml
EGC config: egc-install.json
optional stack map: config/project-stack-mappings.json in the EGC repo

When the EGC checkout is available, use config/project-stack-mappings.json as the stack-to-rules/skills reference. If the file is unavailable, fall back to the installed EGC manifests and explicit user choices.

Planning Flow

Identify the target harness. Default to Gemini unless the user asks for cursor, codex, gemini, opencode, codebuddy, joycode, or qwen.
Detect stacks from project files and show the evidence for each match.
Resolve the smallest useful EGC plan:
- project has an egc-install.json: node scripts/install-plan.js --config egc-install.json --json
- user named a profile: node scripts/install-plan.js --profile <profile> --target <target> --json
- user named skills: node scripts/install-plan.js --skills <skill-ids> --target <target> --json
- only language stacks are detected: use the legacy language install dry-run with those language names
Run a dry-run apply command before writing:

Read the full file on GitHub · 86 lines

Changes

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.

6d ago First seen · 86 lines · 23 tokens per session scan A d59815d04c70

Subscribe to this mod's changes

project-init is a command published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 924 once invoked, about $0.0001 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-09-03.

Building agents Claude Code Project management ai-agents aider cursor mcp persistent memory

project-init

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/project-init

Usage

Safety Rules

Detection Inputs

Planning Flow

What this file has done since we first saw it

Other commands, from other repositories

ijfw-status

pm-done

pm-charter

_closing

task-init

quarterly-okr-review