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 skills add vanessamarely/ai-playbook-reposito --skill ai-tool-setupgit clone --depth 1 https://github.com/vanessamarely/ai-playbook-repositoWrote 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/vanessamarely/ai-playbook-reposito/ai-tool-setup)<a href="https://agentmods.dev/skills/vanessamarely/ai-playbook-reposito/ai-tool-setup"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/ai-tool-setup/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/vanessamarely/ai-playbook-reposito/ai-tool-setup"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/ai-tool-setup.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.00117 | $0.01656 |
| Opus 5 | $0.00059 | $0.00828 |
| Sonnet 5 | $0.00023 | $0.00331 |
| Haiku 4.5 | $0.00012 | $0.00166 |
Grade A, and why
ai-tool-setup 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 11d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: AI Tool Setup
Purpose
Generate or update AI assistant instruction files for GitHub Copilot, Claude Code, Cursor, and OpenAI Codex CLI so all four tools share a consistent set of policies derived from this playbook. Each tool has its own discovery mechanism and file format — this skill does not assume they share a folder.
Inputs
targetTool: One ofcopilot,claude,cursor,codex, orallprojectRoot: Absolute path to the repository rootplaybookRoot: Path to this playbook directory (default:ai-playbook)
Outputs
| Tool | Files written |
|---|---|
| GitHub Copilot | .github/copilot-instructions.md, .github/instructions/frontend.instructions.md, .github/instructions/backend.instructions.md |
| Claude Code | CLAUDE.md, .claude/agents/, .claude/skills/ (copied from playbook, not generated) |
| Cursor | .cursor/rules/workspace-policy.mdc, .cursor/rules/style-output.mdc, plus file-type rules |
| OpenAI Codex CLI | AGENTS.md (root), optional nested AGENTS.md per package |
Plus a summary of files created or updated.
Procedures
1. Validate Inputs
Verify projectRoot exists and contains a recognizable project (check for package.json, pom.xml, or pyproject.toml).
Verify playbookRoot contains .agents/skills/ and policies/.
If either check fails, output an error and exit.
2. Detect Project Type
Execute: node <playbookRoot>/tools/project-detect.mjs <projectRoot>
Extract:
projectType(react, node-typescript, java-maven, python, unknown)frameworklanguage
3. Load Applicable Policies
Always read: <playbookRoot>/policies/workspace-policy.md and <playbookRoot>/policies/style-output.md.
If projectType is react or node-typescript:
- Read:
<playbookRoot>/policies/frontend-policy.md - Read:
<playbookRoot>/policies/backend-policy.md
4. Build Skill Routing Table
Map detected project types to the playbook's skills (see <playbookRoot>/.agents/skills/*/SKILL.md frontmatter for the canonical list — Codex does not distinguish "agent" from "skill", so all 13 procedures live under .agents/skills/).
What ships with it
6 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.
- 11d ago First seen · 140 lines · 117 tokens per session scan A c605bbd419e4
ai-tool-setup is a skill published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 1,656 once invoked, about $0.0006 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.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…