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 scan-workspacegit 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/scan-workspace)<a href="https://agentmods.dev/skills/vanessamarely/ai-playbook-reposito/scan-workspace"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/scan-workspace/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/scan-workspace"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/scan-workspace.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.00052 | $0.00964 |
| Opus 5 | $0.00026 | $0.00482 |
| Sonnet 5 | $0.00010 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
scan-workspace 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Scan Workspace
Purpose
Identify the project type within a target folder, determine which skills apply, and verify that AI tool instruction files (GitHub Copilot, Claude Code, Cursor, OpenAI Codex CLI) are present and up to date.
Inputs
targetFolder: Absolute or relative path to the project root.
Outputs
- JSON structure containing:
projectType: Detected type (e.g.,react,node-service,java-spring,python-fastapi).skills: List of applicable skill identifiers.aiTools: Status of AI instruction files present in the project.warnings: Any issues detected (missing dependencies, inconsistent configuration, missing AI tool files).
Procedure
Step 1: Validate Target Folder
- Verify the folder exists.
- Check read permissions.
- If validation fails, output error and exit.
Step 2: Run Project Detection
Execute: node tools/project-detect.mjs <targetFolder>
Expected output: JSON with project metadata.
If the script fails:
- Check that Node.js is available.
- Verify the script path is correct relative to the playbook root.
- Output the stderr and exit.
Step 3: Parse Detection Results
Extract:
projectTypeframework(if applicable)language- Configuration file paths
Step 4: Map to Skills
Use the following routing table:
| Project Type | Skills |
|---|---|
react |
react-components, a11y-automation |
node-typescript |
node-typescript-service |
java-spring |
(Refer to backend-policy.md; no specific skill yet) |
python-fastapi |
(Refer to backend-policy.md; no specific skill yet) |
unknown |
Fallback to manual inspection |
Step 5: Check AI Tool Instruction Files
For each AI tool, verify the instruction file exists in targetFolder:
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 · 124 lines · 52 tokens per session scan A 1133e214c67e
scan-workspace is a skill published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 964 once invoked, about $0.0003 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…