project-setup

project-setup is a skill for Codex from pinkpixel-dev/agentskills-mcp. It costs 28 tokens per session (1,487 once invoked), scanned A, original, MIT.

A project-starting guide that explains how to create different kinds of software projects and their initial files. It includes an example for creating a Visual Studio Code extension.

In plain words
What is it for?
Use it to choose setup instructions, create project files, and scaffold a VS Code extension with options such as JavaScript or TypeScript, package manager, bundler, and Git.
Why use it?
It helps turn project requirements into a suitable starting structure when beginning with an empty folder.

Skill for Codex

Written for Codex: installed under .codex/.

Good fit Use it to choose setup instructions, create project files, and scaffold a VS Code extension with options such as JavaScript or TypeScript, package manager, bundler, and Git.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pinkpixel-dev/agentskills-mcp/project-setup
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.

Any agent
npx skills add pinkpixel-dev/agentskills-mcp --skill project-setup
Clone the repo
git clone --depth 1 https://github.com/pinkpixel-dev/agentskills-mcp

Made for: 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-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/pinkpixel-dev/agentskills-mcp/project-setup/github.svg)](https://agentmods.dev/skills/pinkpixel-dev/agentskills-mcp/project-setup)
Your own site
<a href="https://agentmods.dev/skills/pinkpixel-dev/agentskills-mcp/project-setup"><img src="https://agentmods.dev/badge/skills/pinkpixel-dev/agentskills-mcp/project-setup/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-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/pinkpixel-dev/agentskills-mcp/project-setup"><img src="https://agentmods.dev/badge/skills/pinkpixel-dev/agentskills-mcp/project-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,487 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01487
Opus 5.5 $0.00011 $0.00595
Sonnet 5.5 $0.00006 $0.00297
Haiku 4.5 $0.00003 $0.00149

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

Security

Grade A, and why

project-setup 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 1mo 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.

.codex/skills/project-setup/SKILL.md · 140 lines

How it starts

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

How to setup a project

Determine what kind of project the user wants to create, then based on that, choose which setup info below to follow. Only setup a project if the folder is empty or if you've just called the tool first calling the tool to create a workspace.

vscode-extension

A template for creating a VS Code extension using Yeoman and Generator-Code.

Run this command:

npx --package yo --package generator-code -- yo code . --skipOpen

The command has the following arguments:

  • -t, --extensionType: Specify extension type: ts, js, command-ts, command-js, colortheme, language, snippets, keymap, extensionpack, localization, commandweb, notebook. Defaults to ts
  • -n, --extensionDisplayName: Set the display name of the extension.
  • --extensionId: Set the unique ID of the extension. Do not select this option if the user has not requested a unique ID.
  • --extensionDescription: Provide a description for the extension.
  • --pkgManager: Specify package manager: npm, yarn, or pnpm. Defaults to npm.
  • --bundler: Bundle the extension using webpack or esbuild.
  • --gitInit: Initialize a Git repository for the extension.
  • --snippetFolder: Specify the location of the snippet folder.
  • --snippetLanguage: Set the language for snippets.

Rules

  1. Do not remove any arguments from the command. Only add arguments if the user requests them.
  2. Call the tool copilot_getVSCodeAPI with the users query to get the relevant references.
  3. After the tool copilot_getVSCodeAPI has completed, only then begin to modify the project.

next-js

A React based framework for building server-rendered web applications.

Run this command:

npx create-next-app@latest .

The command has the following arguments:

  • --ts, --typescript: Initialize as a TypeScript project. This is the default.
  • --js, --javascript: Initialize as a JavaScript project.
  • --tailwind: Initialize with Tailwind CSS config. This is the default.
  • --eslint: Initialize with ESLint config.
  • --app: Initialize as an App Router project.
  • --src-dir: Initialize inside a 'src/' directory.
  • --turbopack: Enable Turbopack by default for development.
  • --import-alias <prefix/*>: Specify import alias to use.(default is "@/*")
  • --api: Initialize a headless API using the App Router.
  • --empty: Initialize an empty project.
  • --use-npm: Explicitly tell the CLI to bootstrap the application using npm.
  • --use-pnpm: Explicitly tell the CLI to bootstrap the application using pnpm.
  • --use-yarn: Explicitly tell the CLI to bootstrap the application using Yarn.
  • --use-bun: Explicitly tell the CLI to bootstrap the application using Bun.

Read the full file on GitHub · 140 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. 1mo ago First seen · 140 lines · 28 tokens per session scan A d052fbb6193d

Subscribe to this mod's changes

project-setup is a skill published in the GitHub repository pinkpixel-dev/agentskills-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,487 once invoked, about $0.0001 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-31.