Borrowing it
Nothing to install: this file belongs to pavel-molyanov/molyanov-ai-dev. 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/pavel-molyanov/molyanov-ai-dev/main/.codex/skills/project-initialization/SKILL.mdgit clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-devWrote 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/pavel-molyanov/molyanov-ai-dev/project-initialization)<a href="https://agentmods.dev/skills/pavel-molyanov/molyanov-ai-dev/project-initialization"><img src="https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/project-initialization/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/pavel-molyanov/molyanov-ai-dev/project-initialization"><img src="https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/project-initialization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 52 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00066 | $0.01087 |
| Opus 5 | $0.00033 | $0.00544 |
| Sonnet 5 | $0.00013 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
project-initialization 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 10d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Initialization
Initialize the project in the current working directory. Existing project files are preserved in
an old* directory for later review; do not merge them into the new scaffold during this workflow.
Dual-Runtime Project Generation
The bundled template contains Claude project sources under .claude/**. Its pre-commit hook runs
the installed ~/.claude/scripts/sync-to-codex.sh converter after those sources are staged. This
generates and stages the matching AGENTS.md and .codex/** runtime before the commit while
.gitignore excludes host-local .codex/.sync/**. A reported conflict or validation error stops
the commit.
1. Check the Current Directory
Work only in the current directory. If it is already a Git repository with uncommitted changes,
ask whether to commit them first, continue while preserving them in old*, or stop. Do not proceed
until the user chooses.
Resolve the directory of this loaded project-initialization skill and set INIT_SKILL_DIR to that
absolute path. Verify that its assets/new-project/ directory exists before moving project files.
2. Preserve Existing Files and Apply the Template
If the current directory contains anything other than .git, move all such entries into the first
available directory named old, old2, old3, and so on. Do not move .git.
OLD_DIR=""
if find . -mindepth 1 -maxdepth 1 ! -name '.git' -print -quit | grep -q .; then
OLD_DIR="old"
N=2
while [ -e "$OLD_DIR" ]; do OLD_DIR="old${N}"; ((N++)); done
mkdir "$OLD_DIR"
find . -mindepth 1 -maxdepth 1 ! -name '.git' ! -name "$OLD_DIR" -exec mv -- {} "$OLD_DIR/" \;
fi
cp -rp "$INIT_SKILL_DIR/assets/new-project/." .
If OLD_DIR is non-empty, inspect it for .env*, *.key, *.pem, credentials.json, and
secrets/. Ensure every sensitive path is covered by the new .gitignore before staging files.
Never print secret contents.
3. Initialize Git and Hooks
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/new-project/.claude/settings.json 42 B
- assets/new-project/.claude/skills/project-knowledge/references/architecture.md 3.7 KB
- assets/new-project/.claude/skills/project-knowledge/references/deployment.md 4.6 KB
- assets/new-project/.claude/skills/project-knowledge/references/patterns.md 3.0 KB
- assets/new-project/.claude/skills/project-knowledge/references/project.md 1.7 KB
- assets/new-project/.claude/skills/project-knowledge/references/ux-guidelines.md 5.1 KB
- assets/new-project/.claude/skills/project-knowledge/SKILL.md 2.9 KB
- assets/new-project/.env.example 0 B
- assets/new-project/.githooks/pre-commit 467 B
- assets/new-project/.gitignore 631 B
- assets/new-project/.mcp.bot.json 120 B
- assets/new-project/.mcp.json 120 B
- assets/new-project/backlog.md 284 B
- assets/new-project/CLAUDE.md 634 B
- assets/new-project/README.md 1.3 KB
- assets/new-project/work/completed/.gitkeep 0 B
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.
- 10d ago First seen · 98 lines · 66 tokens per session scan A 4dbbb9845fee
project-initialization is a skill published in the GitHub repository pavel-molyanov/molyanov-ai-dev (285 stars, last pushed 17d ago), licensed MIT. It adds 66 tokens to every session and 1,087 once invoked, about $0.0003 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 skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.