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.
npx agentmods add skills/p2ergmbh/agentic-coding/project-setupnpx skills add P2ERGmbH/agentic-coding --skill project-setupgit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWhat 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 | $0.00039 | $0.00869 |
| Opus 5 | $0.00019 | $0.00434 |
| Sonnet 5 | $0.00008 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project & Agent Setup Workflow
This skill is used to initialize or update a project's settings, define stakeholders for automated agent notifications/@mentions, configure environment variables (.env), and generate matching MCP server configurations for the user's chosen agentic CLI.
Trigger
Use this skill when:
- Setting up a new repository with this agentic ruleset.
- The user asks to "configure the project", "setup the agents", "run project setup", or "setup mcp servers".
- An agent detects that both the
package.json"agents"block anddocs/project.jsonare missing or incomplete during startup checks.
Phase 1: Stakeholder & Project Configuration (package.json or docs/project.json)
The single source of truth for repository details and stakeholder GitHub usernames for mentions and reviews is stored in the package.json file under the "agents" configuration key. If package.json is missing or uninitialized, the workflow automatically falls back to docs/project.json.
1.1 Checked Configuration Schema
Every agent session must verify if package.json (under "agents") or docs/project.json exists. The expected schema structure is:
{
"projectName": "your-project-name",
"organization": "your-github-org",
"repository": "your-github-repo",
"stakeholders": {
"productManager": "@pm-github-username",
"seniorDeveloper": "@senior-dev-username",
"qaLead": "@qa-lead-username",
"techArchitect": "@architect-username"
},
"environments": {
"production": "https://your-domain.com",
"development": "https://dev.your-domain.com",
"localPort": 6767
}
}
1.2 Interactive Setup Script
To easily create or update this file without manual JSON editing, run the bundled interactive setup script:
npx node .agents/skills/project-setup/scripts/setup.js
Phase 2: Environment Credentials
During the setup process, the user is prompted for their API tokens. These are written directly to .env or .env.local to enable seamless integration with Figma and GitHub REST APIs:
What ships with it
1 file 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.
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.
- 2d ago First seen · 91 lines · 39 tokens per session scan A 1c2ae8d085c9
project-setup is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 869 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…