What is project-tooling?

A project-checking guide that looks at a project's own notes, commands, and helper folders before work begins. It checks .tooling.md, package.json scripts, and scripts/ and tools/ directories.

Use it before editing, diagnosing, testing, building, or deploying a project so its existing scripts and operational helpers are taken into account.

It reduces guesswork by showing which commands and practices the project already expects you to use.

project-tooling — Skill for Claude Code and Codex by scott-fryxell

Install

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.

Any agent

npx skills add scott-fryxell/brayness --skill project-tooling

Clone the repo

git clone --depth 1 https://github.com/scott-fryxell/brayness

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/scott-fryxell/brayness/project-tooling/github.svg)](https://agentmods.dev/skills/scott-fryxell/brayness/project-tooling)

Your own site

<a href="https://agentmods.dev/skills/scott-fryxell/brayness/project-tooling"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/project-tooling/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/scott-fryxell/brayness/project-tooling"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/project-tooling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 561 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.

Model	Per session	Once invoked
Fable 5.1	$0.00122	$0.00561
Opus 5.5	$0.00049	$0.00224
Sonnet 5.5	$0.00024	$0.00112
Haiku 4.5	$0.00012	$0.00056

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

Security

Grade A, and why

project-tooling 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 28d 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.

skills/project-tooling/SKILL.md · 38 lines

What it actually says

Project Tooling

Before working in a work/<project>, know what tooling it ships before you guess. The project's own scripts and helpers are the first thing to reach for when diagnosing, testing, building, or deploying.

Do this first

In the project directory (work/<project>), check:

.tooling.md (if present) - curated notes. This is the highest-signal source: it names the high-value diagnostic commands and their usage, plus caveats a raw script list can't convey (e.g. "realness check is docs/vp check, not type checking").
package.json scripts - the full script list. Group by purpose (test / lint / type / build / deploy / logs / dev) when deciding what runs what.
scripts/ dir - shell/JS helper scripts.
tools/ dir - admin/ops data scripts (often need a service account or env var).

Prefer the project's existing npm run ... scripts over raw tooling or reinventing a command. Run from that project's directory.

If a `.tooling.md` is missing

The scripts, scripts/, and tools/ dirs are still authoritative - read package.json and list the dirs directly. Consider proposing a .tooling.md if the project has enough tooling that it would help future sessions.

Curated files known to exist

work/seeq-app/.tooling.md - heavy logging (logs:errors, logs:search), admin data tools, emulators, deploy.
work/realness-ops/.tooling.md - thin proxy to functions/ + ops tools (traffic, ads).
work/brayness/.tooling.md - the control/live split, the webspace CLI in control/, and the four directions.

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.

28d ago Changed · +1 lines 6800db246719
1mo ago First seen · 37 lines · 122 tokens per session scan A 89837444feca

Subscribe to this mod's changes

project-tooling is a skill published in the GitHub repository scott-fryxell/brayness (125 stars, last pushed 29d ago), licensed MIT. It adds 122 tokens to every session and 561 once invoked, about $0.0005 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.

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens