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/amanktyr/tailor/project-initnpx skills add AmanKtyr/Tailor --skill project-initgit clone --depth 1 https://github.com/AmanKtyr/TailorWrote 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/amanktyr/tailor/project-init)<a href="https://agentmods.dev/skills/amanktyr/tailor/project-init"><img src="https://agentmods.dev/badge/skills/amanktyr/tailor/project-init.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00853 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
project-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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Initialization Skill
Activate this skill when bootstrapping a new project from scratch, establishing architectural baselines, or executing /init-project.
Operational Directive: Never write code before establishing product scope, technical requirements, and developer expertise.
1. Product Discovery Questionnaire
Before recommending or installing any framework, gather critical product invariants:
- Target Product & Core Value Proposition: What is being built, what core problem does it solve, and who are the primary users?
- Platform & Modality: Public SaaS, internal dashboard, mobile API, desktop application, or developer CLI?
- Scale & Traffic Expectations: Prototype / MVP, internal team tool (<100 users), or high-throughput multi-tenant production system?
- Data Model & Concurrency: Relational data (PostgreSQL/MySQL), document-based (MongoDB), key-value cache (Redis), or embedded (SQLite)?
- Deployment & Runtime Constraints: Serverless (Vercel/Cloudflare Workers), containerized cluster (Docker/Kubernetes), single VPS, or static hosting?
2. Developer Expertise Matrix
Assess the developer's familiarity level (Beginner, Intermediate, Advanced, Expert):
- Languages: TypeScript, Python, Go, Rust, C#, PHP, Java
- Frontend Frameworks: Next.js (App Router), React (SPA), Vue / Nuxt, SvelteKit, Vanilla HTML/CSS
- Backend Frameworks: Express / Fastify, NestJS, Django / FastAPI, Go Gin / Echo, ASP.NET Core, Laravel
- Databases & ORMs: Prisma, Drizzle, TypeORM, SQLAlchemy, Django ORM, Entity Framework Core, Raw SQL
Rule: Never recommend a complex, unfamiliar stack for an urgent MVP if a well-understood, robust alternative achieves the goal in half the time.
3. Technology Stack Recommendation Matrix
| Project Archetype | Recommended Stack | Key Rationale |
|---|---|---|
| Full-Stack SaaS / Web App | Next.js (App Router) + TypeScript + Tailwind CSS + PostgreSQL + Prisma/Drizzle | Unified language, fast server-side rendering, robust ORM, rapid UI iterations |
| High-Performance API Service | Go (net/http + Gin) OR FastAPI (Python) + PostgreSQL + Redis | High concurrency, low memory footprint, strict typing, auto-generated OpenAPI |
| Data Science / ML Backend | Python + FastAPI + PyTorch / Scikit-learn + PostgreSQL + Celery/Redis | Native ML ecosystem support, async performance, robust data processing |
| Enterprise Internal Tool | Next.js + React + shadcn/ui + PostgreSQL + Supabase / Auth.js | Rapid scaffolding, enterprise UI primitives, integrated authentication |
| Fast Developer CLI Tool | Node.js (TypeScript + Commander + Picocolors) OR Rust (Clap) | Zero-config distribution via npx, fast startup, deterministic execution |
| Micro-Service / Embedded | Go OR Rust + SQLite / PostgreSQL | Zero runtime dependencies, single static binary, instant cold start |
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.
- 3d ago First seen · 61 lines · 30 tokens per session scan A b4a5789dc657
project-init is a skill published in the GitHub repository AmanKtyr/Tailor (3 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 853 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…