Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasnpx agentmods add skills/tahirraufkeeyu/software-development-agent-stack--sdas/project-bootstrapWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/project-bootstrap)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/project-bootstrap"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/project-bootstrap.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.1 | $0.00084 | $0.01656 |
| Opus 5 | $0.00042 | $0.00828 |
| Sonnet 5 | $0.00017 | $0.00331 |
| Haiku 4.5 | $0.00008 | $0.00166 |
Grade A, and why
project-bootstrap 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 6d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User says "start a new project", "scaffold a service", "bootstrap a repo".
- User wants to convert a single-file prototype into a proper package.
- User wants to standardise a team repo layout.
Do not use this skill to add a feature to an existing project or to migrate between stacks — those require narrower changes.
Inputs
- Stack: one of
ts-node,py-fastapi,go,rust. - Project name (used for package name, module path, CLI binary).
- Optional: license (
MIT,Apache-2.0,BSD-3-Clause, proprietary). DefaultMIT. - Optional: CI provider (
githubdefault), container target (alpineordistroless). - Optional: author/org for license and package metadata.
Outputs
A directory tree for the chosen stack with these always present:
- Formatter config (prettier / black+isort / gofmt+goimports / rustfmt).
- Linter config (eslint / ruff / golangci-lint / clippy).
- Test harness and a smoke test.
- Pre-commit hook config (
.pre-commit-config.yamlor equivalent). - GitHub Actions workflow running lint, type-check, test on PRs.
.gitignoretailored to the stack.README.mdskeleton (seedocumentationskill).- License file.
- Dockerfile (multi-stage, non-root, pinned base image).
.editorconfigand.gitattributes.
Tool dependencies
- Write / Edit for file creation.
- Bash for the user to run
git init,npm init -y, etc. Do not invoke tools that mutate their environment unless the user asks. - See references/stack-templates.md for exact config snippets per stack.
Procedure
-
Confirm inputs. If the stack is ambiguous, ask. If a target directory exists and is non-empty, refuse to overwrite without explicit confirmation.
-
Create the directory tree for the stack:
ts-node:src/,src/index.ts,tests/,package.json,tsconfig.json,.eslintrc.cjs,.prettierrc,vitest.config.ts.py-fastapi:src/<pkg>/,src/<pkg>/__init__.py,src/<pkg>/main.py,tests/,tests/test_smoke.py,pyproject.toml.go:cmd/<name>/main.go,internal/,go.mod,Makefile.rust:src/main.rsorsrc/lib.rs,Cargo.toml,rustfmt.toml,clippy.toml.
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.
- 6d ago First seen · 179 lines · 84 tokens per session scan A 3dd40c8cfeb7
project-bootstrap is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 1,656 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…