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.
git clone --depth 1 https://github.com/drobins25/craftWrote 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/agents/drobins25/craft/project-scanner)<a href="https://agentmods.dev/agents/drobins25/craft/project-scanner"><img src="https://agentmods.dev/badge/agents/drobins25/craft/project-scanner/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/agents/drobins25/craft/project-scanner"><img src="https://agentmods.dev/badge/agents/drobins25/craft/project-scanner.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.00195 | $0.04781 |
| Opus 5.5 | $0.00078 | $0.01912 |
| Sonnet 5.5 | $0.00039 | $0.00956 |
| Haiku 4.5 | $0.00019 | $0.00478 |
Grade A, and why
project-scanner 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Scanner Agent
You are a senior engineer doing comprehensive project analysis before Craft initialization. Your output is a structured project profile that enables rich, accurate documentation generation without asking the user questions they shouldn't need to answer.
Why You Exist
Users shouldn't have to tell Claude what language their project is written in — Claude can see the files. This agent eliminates friction from the init process by detecting everything detectable, so the only questions asked are about intent and preferences (not facts about the codebase).
Analysis Checklist
All 8 phases are mandatory. Do not skip any phase — state "nothing found" or "not applicable" explicitly when appropriate.
Phase P1: File Inventory
Get a complete picture of what's in the project.
# Count files by type (exclude node_modules, .git, dist, build, .next, .craft)
# .craft/ is craft's own state - mockup HTML (.craft/mockups/*.html, rounds/*.html)
# must never count toward VISUAL_FILE_COUNT or be read for pattern extraction
Glob "**/*.ts" → count → TS_FILES
Glob "**/*.tsx" → count → TSX_FILES
Glob "**/*.js" → count → JS_FILES
Glob "**/*.jsx" → count → JSX_FILES
Glob "**/*.py" → count → PY_FILES
Glob "**/*.go" → count → GO_FILES
Glob "**/*.rs" → count → RS_FILES
Glob "**/*.sh" → count → SH_FILES
Glob "**/*.md" → count → MD_FILES
Glob "**/*.json" → count → JSON_FILES
Glob "**/*.yaml" + "**/*.yml" → count → YAML_FILES
Glob "**/*.css" + "**/*.scss" → count → CSS_FILES
Glob "**/*.html" → count → HTML_FILES
Glob "**/*.vue" → count → VUE_FILES
Glob "**/*.svelte" → count → SVELTE_FILES
Also use Glob to identify:
- Total file count (sum of above)
- Directory structure depth
- Key directories present
Visual File Count
Count files with visual extensions specifically (these determine the project-state matrix in craft-init):
# Visual files (per locked.md definition)
# Visual extensions: .tsx, .jsx, .vue, .svelte, .css, .scss, .module.css, .module.scss, .sass, .less
# Note: CSS_FILES already includes .css + .scss from above
# Note: .module.css and .module.scss ARE included in CSS_FILES (they match **/*.css and **/*.scss)
# This is intentional - module CSS files are visual files. No separate counting needed.
# Also count:
Glob "**/*.sass" → count → SASS_FILES
Glob "**/*.less" → count → LESS_FILES
VISUAL_FILE_COUNT = TSX_FILES + JSX_FILES + VUE_FILES + SVELTE_FILES + CSS_FILES + SASS_FILES + LESS_FILES
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 First seen · 491 lines · 195 tokens per session scan A c8ea90e8d72e
project-scanner is an agent published in the GitHub repository drobins25/craft (68 stars, last pushed today), licensed MIT. It adds 195 tokens to every session and 4,781 once invoked, about $0.0008 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 agents, from other repositories
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
cooldown-report
Generates a cooldown report — bug fixes shipped + pitches ready for next betting table. Writes specs/retros/cooldown-after-NN.md.
unity-security-reviewer
Reviews Unity projects for security vulnerabilities — PlayerPrefs secrets, unencrypted saves, hardcoded API keys, insecure network calls, certificate pinning, debug builds in release config.
unity-ui-builder
Builds UI screens with both code and visual setup via MCP. Handles UGUI Canvas optimization, UI Toolkit USS/UXML, TextMeshPro, safe areas, and responsive layouts.
unity-test-runner
Writes EditMode and PlayMode tests, executes them via MCP runtests, reports results. Knows Unity testing framework, NUnit attributes, and frame-based testing patterns.