initialize-project

initialize-project is a skill for Claude Code, Codex from yu-iskw/skill-inspector. It costs 48 tokens per session (485 once invoked), scanned A, original, Apache-2.0.

A setup process for turning a TypeScript project template into a new project by replacing its placeholder names, descriptions, author details, and documentation.

In plain words
What is it for?
Use it when creating a project from the template, renaming its packages, updating its README, and installing dependencies so the lockfile matches.
Why use it?
Starting from a template can leave old project names and package references in several files. This process gathers the new details and updates the main project files consistently.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/yu-iskw/skill-inspector/initialize-project
Any agent
npx skills add yu-iskw/skill-inspector --skill initialize-project
Clone the repo
git clone --depth 1 https://github.com/yu-iskw/skill-inspector

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 initialize-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/yu-iskw/skill-inspector/initialize-project.svg)](https://agentmods.dev/skills/yu-iskw/skill-inspector/initialize-project)
Your own site
<a href="https://agentmods.dev/skills/yu-iskw/skill-inspector/initialize-project"><img src="https://agentmods.dev/badge/skills/yu-iskw/skill-inspector/initialize-project.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 485 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.00485
Opus 5 $0.00024 $0.00243
Sonnet 5 $0.00010 $0.00097
Haiku 4.5 $0.00005 $0.00049

Measured 4d ago against content hash 9dc21d46f27f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/initialize-project/SKILL.md · 41 lines

What it actually says

Initialize Project

Purpose

This skill automates the initial setup of a new project derived from this template. It leverages AI capabilities to directly modify project metadata and documentation by replacing placeholders, ensuring a clean start for a new repository.

Instructions

  1. Gather Information: Ask the user for:
    • New project name (e.g., my-awesome-app)
    • Project description
    • Author name
    • (Optional) GitHub repository URL
  2. Update Project Metadata: Directly update the following files using the Write or StrReplace tools:
    • package.json: Update name, description, and author.
    • packages/common/package.json: Update the package name to match the new scope (e.g., @new-name/common).
    • .trunk/trunk.yaml: If there are template-specific references, update them.
  3. Update README Placeholders: Use the StrReplace tool to replace the placeholders in README.md with the gathered information:
    • {PROJECT_NAME} -> New project name
    • {PROJECT_DESCRIPTION} -> Project description
    • {LICENSE} -> ISC (or other preferred license)
  4. Install Dependencies: Run pnpm install to update the lockfile with the new package names.
  5. Final Cleanup: Remove the initialization skill and its related files once bootstrapping is complete, if requested by the user.

Examples

Example 1: Initializing a new CLI tool

Input: User says "Initialize this project as 'json-fixer', a CLI tool to fix broken JSON files." Action:

  1. Gather details from the user (Name: json-fixer, Description: A CLI tool to fix broken JSON files, Author: [Author Name]).
  2. Update package.json with the new metadata.
  3. Use StrReplace on README.md to swap {PROJECT_NAME}, {PROJECT_DESCRIPTION}, and {LICENSE} with the actual values.
  4. Run pnpm install.
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. 4d ago First seen · 41 lines · 48 tokens per session scan A 9dc21d46f27f

Subscribe to this mod's changes

initialize-project is a skill published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 19d ago), licensed Apache-2.0. It adds 48 tokens to every session and 485 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

implementing-devsecops-security-scanning

Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…

xalgorix/xalgorix · 109 tokens

scanning-containers-with-trivy-in-cicd

This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…

xalgorix/xalgorix · 74 tokens

implementing-code-signing-for-artifacts

This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…

xalgorix/xalgorix · 62 tokens

implementing-semgrep-for-custom-sast-rules

Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.

xalgorix/xalgorix · 37 tokens

integrating-dast-with-owasp-zap-in-pipeline

This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…

xalgorix/xalgorix · 76 tokens

performing-sca-dependency-scanning-with-snyk

This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…

xalgorix/xalgorix · 77 tokens