molyanov-ai-dev: Skill for Claude Code

.agents/skills/project-initialization/SKILL.md

project-initialization is a skill for Claude Code, Codex from pavel-molyanov/molyanov-ai-dev. It costs 71 tokens per session (1,312 once invoked), scanned A, original, MIT.

A project setup workflow based on a standard template for projects that run in two supported environments. It preserves existing files for later review, configures Git hooks, and can create or connect a private GitHub repository with main and development branches.

In plain words
What is it for?
Use it to initialize a new project, preserve an existing directory's contents, set up Git hooks, and prepare branches and a private GitHub repository. It requires a decision first if the directory already contains uncommitted Git changes.
Why use it?
It gives a new project a consistent starting structure while reducing the risk of losing files already in the directory. It also prepares the project files used by the supported coding-agent runtimes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; reads ~/.codex paths.

This is pavel-molyanov/molyanov-ai-dev's own configuration. It tells Claude Code and Codex how to work on molyanov-ai-dev itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything molyanov-ai-dev configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/pavel-molyanov/molyanov-ai-dev/main/.agents/skills/project-initialization/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-dev

Made for: Claude Code, Codex.

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.

agentmods badge for project-initialization

README.md
[![agentmods](https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/project-initialization/github.svg)](https://agentmods.dev/skills/pavel-molyanov/molyanov-ai-dev/project-initialization)
Your own site
<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.

agentmods 80×15 button for project-initialization

Your own site · 80×15
<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>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,312 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
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.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.01312
Opus 5.5 $0.00028 $0.00525
Sonnet 5.5 $0.00014 $0.00262
Haiku 4.5 $0.00007 $0.00131

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

Security

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

.agents/skills/project-initialization/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 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 Git hooks use the installed ~/.claude/scripts/codex-sync-git-guard.py: pre-commit generates and stages AGENTS.md, .agents/skills/**, and .codex/agents/** after the sources are staged; pre-push checks for drift. Host-local .codex/.sync/** is ignored. A reported conflict or validation error stops the action.

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.

Determine whether this is a software project (main + dev) or a skills workspace (main only). Use the request and existing project context; ask if the type is unclear.

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, add its exact root-relative directory (for example /old2/) to the new root .gitignore. Keep the archive local and untracked so Git hooks do not treat its saved Claude configuration as another active project. Do not stage the archive.

Read the full file on GitHub · 108 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.

  1. 6d ago Changed · +10 lines · +5 tokens per session 1d3245dce31e
  2. 1mo ago First seen · 98 lines · 66 tokens per session scan A 4dbbb9845fee

Subscribe to this mod's changes

project-initialization is a skill published in the GitHub repository pavel-molyanov/molyanov-ai-dev (300 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 1,312 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

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.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

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 zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens