Borrowing it
Nothing to install: this file belongs to P2ERGmbH/agentic-coding. 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/P2ERGmbH/agentic-coding/main/.agents/skills/project-setup/SKILL.mdgit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWrote 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/p2ergmbh/agentic-coding/project-setup)<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/project-setup"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/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.
<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/project-setup"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/project-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00039 | $0.00869 |
| Opus 5.5 | $0.00016 | $0.00348 |
| Sonnet 5.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 2mo 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.
- 2mo 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 4mo ago), licensed MIT. It adds 39 tokens to every session and 869 once invoked, about $0.0002 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.