A project setup guide that creates or reconciles documentation, coding standards, architecture notes, and architecture decision records (ADRs). It works for both new and existing code repositories.

Use it to initialise project documentation, record existing conventions, define engineering standards, and prepare architecture decision records.

It removes the need to invent a documentation structure or guess which conventions an existing project follows. It also keeps a complex setup process organised with visible tasks and required checks.

init — Skill for Claude Code and Codex by shahidshabbir-se/my-pi-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 shahidshabbir-se/my-pi-setup --skill init

Clone the repo

git clone --depth 1 https://github.com/shahidshabbir-se/my-pi-setup

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/init/github.svg)](https://agentmods.dev/skills/shahidshabbir-se/my-pi-setup/init)

Your own site

<a href="https://agentmods.dev/skills/shahidshabbir-se/my-pi-setup/init"><img src="https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/init/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/shahidshabbir-se/my-pi-setup/init"><img src="https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,383 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.

Model	Per session	Once invoked
Fable 5.1	$0.00025	$0.03383
Opus 5.5	$0.00010	$0.01353
Sonnet 5.5	$0.00005	$0.00677
Haiku 4.5	$0.00003	$0.00338

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

Security

Grade A, and why

init 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 19d 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.

agent/skills/init/SKILL.md · 259 lines

How it starts

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

Init

Set up a project's documentation and standards from scratch or reconcile existing conventions with best practices.

When to use

User says "init", "set up docs", "setup project", "initialize docs", or runs /init
New project needs documentation scaffolding
Existing project needs its conventions documented

Task tracking

At the very start of init, create the following tasks using TaskCreate:

Detection (Explore)
Grilling + Skill opportunities
Producing core files
Skills proposal (Phase 5)
Report + Commit

Use TaskUpdate to mark them in progress or complete as you move through phases. Use TaskList to review status when needed.

This keeps complex init sessions organized and visible.

Hard Gates (non-negotiable)

Phase 2 gate: Phase 4 cannot begin until Phase 2's frontier is empty. This means: keep asking ask_user_question rounds of exactly 3, recomputing the frontier after every round, until either (a) the frontier is empty, or (b) every remaining frontier item has an explicit skip-list entry with path:line evidence or a stated reason it can't be resolved by asking. A single answered round does not satisfy this gate by itself — if the frontier still has open items after a round, ask another round. "User was quiet" is not a skip. Existing CONTEXT.md is evidence for those terms only.
Phase 5 gate: Phase 6 cannot begin until the interactive proposal in Phase 5 has been reviewed and explicitly approved by the user.
No main-session scanning: Phase 1 must use Explore. Main session may only read paths named by Explore.
No web_search in main session: Research gaps must spawn a researcher subagent.

Phase 1 — Detection

Spawn one Explore subagent and wait for the result:

subagent_spawn({ agentType: "explore", prompt: "..." })

Non-coding project detection (enhanced): After Explore results, check for strong non-coding signals:

High ratio of documentation files (.md, .txt, docs/, content/)
Absence of source code folders (src/, apps/, packages/*/src)
No package manifests (package.json, pyproject.toml, Cargo.toml, go.mod)
Presence of research/writing-oriented files

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

19d ago First seen · 259 lines · 25 tokens per session scan A 0e4c11aef603

Subscribe to this mod's changes

init is a skill published in the GitHub repository shahidshabbir-se/my-pi-setup (2 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 3,383 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-09-27.

Planning Writing and docs agents ai-coding ai-workflow automation coding-agent developer-tools

repo-hygiene

Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.

QwenLM/qwen-code · 48 tokens

browser-use

Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.

QwenLM/qwen-code · 21 tokens

test-failure-explorer

Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.

QwenLM/qwen-code · 32 tokens

google-agents-cli-scaffold

This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…

google/agents-cli · 135 tokens

find-simplifications

Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…

QwenLM/qwen-code · 103 tokens

ccc

This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…

cocoindex-io/cocoindex-code · 80 tokens