folder-audit

A project-structure checker for organizing folders and context files into five layers, from the project map to temporary work files. It also checks the tools used by the project.

In plain words
What is it for?
Use it to review a project's folder layout, context files, reference material, working files, and tool setup against the ICM hierarchy.
Why use it?
It helps find misplaced information, missing context, and common folder-structure problems before they make an agent or developer harder to guide.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/mcmespinaa/folder-structure-protocol/folder-audit
Any agent
npx skills add mcmespinaa/folder-structure-protocol --skill folder-audit
Clone the repo
git clone --depth 1 https://github.com/mcmespinaa/folder-structure-protocol

Made for: Claude Code, Codex.

Per session 135 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,860 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00135 $0.03860
Opus 5 $0.00068 $0.01930
Sonnet 5 $0.00027 $0.00772
Haiku 4.5 $0.00014 $0.00386

Measured 2d ago against content hash 5fd0e967195d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

folder-audit 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 2d 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.

.claude/skills/folder-audit/SKILL.md · 332 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 332 lines · 135 tokens per session scan A 5fd0e967195d

Subscribe to this mod's changes

folder-audit is a skill published in the GitHub repository mcmespinaa/folder-structure-protocol (6 stars, last pushed 1mo ago), with no licence file. It adds 135 tokens to every session and 3,860 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

multi-agent-room

Orchestrate a team of named subagents in shared threads. One orchestrator drives multiple peers with distinct identities; each subagent sees its own inbox and can cross-check findings by posting to a thread the peer is a member of.

Goldziher/basemind · 51 tokens

feature-tracking

Maintain portable Feature Track docs for project features. Use when designing, planning, implementing, reviewing, or finishing feature work; creating or updating PRD/API/design/implementation docs; adding a new feature; or validating docs/features.

JunsW/feature-track · 49 tokens

issue-triage

Read all open issues (GitHub/GitLab), categorize by type and effort, plan batch implementation order, and coordinate implementation across multiple issues in a single PR/MR. Auto-detects platform from git remote. Use when asked to "implement all issues", "fix all open issues", "batch implement", or "address all…

d-oit/rust-2026-template · 102 tokens

kanban-orchestrator

Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically…

kevinnft/ai-agent-skills · 74 tokens

long-task-workflow

Author, preflight, execute, resume, verify, or close one complete Single-Goal Delivery Contract in the currently selected host execution Goal and workspace. Use only when explicitly invoked or a valid common-dir active authority binding exists.

Seven128/project-tiny-context-harness · 50 tokens

status

Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concerns, and compilation sync status.

tim-mccrimmon/structured-context-spec · 31 tokens