Borrowing it
Nothing to install: this file belongs to MaximilianMayr94/skills. 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/MaximilianMayr94/skills/main/.github/skills/init/SKILL.mdgit clone --depth 1 https://github.com/MaximilianMayr94/skillsWrote 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/maximilianmayr94/skills/init)<a href="https://agentmods.dev/skills/maximilianmayr94/skills/init"><img src="https://agentmods.dev/badge/skills/maximilianmayr94/skills/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.
<a href="https://agentmods.dev/skills/maximilianmayr94/skills/init"><img src="https://agentmods.dev/badge/skills/maximilianmayr94/skills/init.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.00024 | $0.00392 |
| Opus 5.5 | $0.00010 | $0.00157 |
| Sonnet 5.5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
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 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.
What it actually says
Phase 1 - Scan
Scan the whole project for existing documentation, architecture, code quality, test quality, bugs, gaps, problems and contradicting information. Use this as input for the interview and the generated documents. Do not assume that the existing information is correct. If the project is empty progress to phase 2 with the ``context.default.mdandsoftware_requirements.default.md` as input for the interview and generated documents.
Phase 2 - Discuss
Ask the user about:
- project purpose, process, tech stack, quality and test expectations,
- product scope, actors, user flows, detailed functionality, acceptance criteria and data contracts,
- bugs, gaps, problems and contradictions in existing material.
- Every few questions (max. 5) ask the user if he wants to progress to phase 3 or if he wants to continue refining with more questions.
- For each question give the user a custom answer field so he can enter something else
Phase 3 - Create documents
- Create
copilot/context.mdin the target project usingcontext.default.md(this folder) as template. - Create
copilot/software_requirements.mdin the target project usingsoftware_requirements.default.md(this folder) as template. - Fill every section from interview answers and project scan.
- Achieve a high-quality complete overview so architecture and implementation can be done without further questions. The better these documents are, the better architecture and implementation will be. Do not rush this step.
- Reference content instead of copying it.
What ships with it
2 files 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.
- 1mo ago First seen · 27 lines · 24 tokens per session scan A 64f6420822a5
init is a skill published in the GitHub repository MaximilianMayr94/skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 392 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…