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/gsa-tts/agentic-coding-playbook/project-bootstrapnpx skills add GSA-TTS/agentic-coding-playbook --skill project-bootstrapgit 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.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.00017 | $0.01912 |
| Opus 5 | $0.00009 | $0.00956 |
| Sonnet 5 | $0.00003 | $0.00382 |
| Haiku 4.5 | $0.00002 | $0.00191 |
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 5d 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 — 233 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.
Note: The universal
AGENTS.mdis deliberately not copied into the target repo. It is the single source of truth for the universal behavioral rules and is expected to be made available to the agent globally. The thin projectAGENTS.mdemitted here declares that universal contract as a prerequisite and instructs the agent to STOP — and require the user's affirmative permission to proceed — if it is unavailable.
Procedure
Step 0: Validate Environment and Plan
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.
- 5d 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 (23 stars, last pushed 3d ago), licensed CC0-1.0. It adds 17 tokens to every session and 1,912 once invoked, about $0.0001 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…