scan-workspace

scan-workspace is an agent for Claude Code from vanessamarely/ai-playbook-reposito. It costs 21 tokens per session (975 once invoked), scanned A, original, MIT.

An agent that examines a project folder to identify what kind of software project it contains and which development instructions apply. It also checks whether configuration files for several AI coding tools are present and current.

In plain words
What is it for?
Use it to detect project types such as React, Node.js services, Java Spring, or Python FastAPI, find applicable skills, and report setup warnings.
Why use it?
It removes the guesswork involved in starting work in an unfamiliar workspace and highlights missing or inconsistent setup.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is "../policies/workspace-policy.md",.

Good fit Use it to detect project types such as React, Node.js services, Java Spring, or Python FastAPI, find applicable skills, and report setup warnings.

Compare 6 agents from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/vanessamarely/ai-playbook-reposito
agentmods
npx agentmods add agents/vanessamarely/ai-playbook-reposito/scan-workspace

Made for: Claude Code.

Wrote 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.

agentmods badge for scan-workspace

README.md
[![agentmods](https://agentmods.dev/badge/agents/vanessamarely/ai-playbook-reposito/scan-workspace/github.svg)](https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/scan-workspace)
Your own site
<a href="https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/scan-workspace"><img src="https://agentmods.dev/badge/agents/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.

agentmods 80×15 button for scan-workspace

Your own site · 80×15
<a href="https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/scan-workspace"><img src="https://agentmods.dev/badge/agents/vanessamarely/ai-playbook-reposito/scan-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 975 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00975
Opus 5 $0.00010 $0.00487
Sonnet 5 $0.00004 $0.00195
Haiku 4.5 $0.00002 $0.00097

Measured 10d ago against content hash b174643596c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

ai-playbook/.claude/agents/scan-workspace.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scan Workspace Agent

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, 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

  1. Verify the folder exists.
  2. Check read permissions.
  3. 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:

  • projectType
  • framework (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:

Read the full file on GitHub · 127 lines

Changes

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.

  1. 10d ago First seen · 127 lines · 21 tokens per session scan A b174643596c3

Subscribe to this mod's changes

scan-workspace is an agent published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 975 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-31.