Borrowing it
Nothing to install: this file belongs to GSA-TTS/agentic-coding-playbook. 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/GSA-TTS/agentic-coding-playbook/main/.agents/skills/project-bootstrap/SKILL.mdgit clone --depth 1 https://github.com/GSA-TTS/agentic-coding-playbookWrote 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/gsa-tts/agentic-coding-playbook/project-bootstrap)<a href="https://agentmods.dev/skills/gsa-tts/agentic-coding-playbook/project-bootstrap"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/project-bootstrap/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/gsa-tts/agentic-coding-playbook/project-bootstrap"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/project-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 190 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00017 | $0.02158 |
| Opus 5.5 | $0.00007 | $0.00863 |
| Sonnet 5.5 | $0.00003 | $0.00432 |
| Haiku 4.5 | $0.00002 | $0.00216 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Project Bootstrap
Set up a complete federal coding project from a single PROJECT_PLAN.md file.
When to Use
- Starting a new project from scratch
- User says "set up a new repo" or "bootstrap this project"
- A PROJECT_PLAN.md file exists but the repo is empty/minimal
Prerequisites
- PROJECT_PLAN.md exists in the target repository root
- The sections Project Identity, Tech Stack, and Compliance Level must be filled in
- Access to the playbook repo (this repo) for source files
Files Copied from Playbook to Target Repo
This skill copies the following files from the playbook repo into the target repository. If a file already exists in the target repo, ask the user before overwriting.
| Source (this repo) | Destination (target repo) | Purpose |
|---|---|---|
templates/AGENTS.md.template |
AGENTS.md |
Thin project-layer agent contract (references the universal contract; customized per project) |
docs/CODING_PRACTICES.md |
docs/CODING_PRACTICES.md |
Secure coding standards |
templates/CONTEXT-GUIDE.project.md |
CONTEXT-GUIDE.md |
Agent context routing (project-scoped) |
templates/risk-assessment.md |
docs/risk-assessment.md |
Risk assessment (pre-filled from plan) |
checklists/pre-deployment.md |
checklists/pre-deployment.md |
62-item pre-deployment checklist |
The agent must have access to these files — either via the playbook repo cloned locally, or by fetching from the playbook repository.
| Path | Kind | Notes |
|---|---|---|
templates/AGENTS.md.template |
playbook-source | See AGENTS.md §13.1a if not found at this relative path. |
docs/CODING_PRACTICES.md |
playbook-source | See AGENTS.md §13.1a if not found at this relative path. |
templates/CONTEXT-GUIDE.project.md |
playbook-source | See AGENTS.md §13.1a if not found at this relative path. |
templates/risk-assessment.md |
playbook-source | See AGENTS.md §13.1a if not found at this relative path. |
checklists/pre-deployment.md |
playbook-source | See AGENTS.md §13.1a if not found at this relative path. |
docs/adr/001-initial-architecture.md |
target-project | Output example in Step 5 — the target project's own first ADR; never resolved via §13.1a. |
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 Changed · +12 lines 1e278b0ae3fe
- 1mo ago First seen · 233 lines · 17 tokens per session scan A 718c24999263
project-bootstrap is a skill published in the GitHub repository GSA-TTS/agentic-coding-playbook (37 stars, last pushed yesterday), licensed CC0-1.0. It adds 17 tokens to every session and 2,158 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-30.
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…