folder-structure-blueprint-generator

folder-structure-blueprint-generator is a skill for Claude Code, Codex from OKHP3/skillz. It costs 72 tokens per session (2,939 once invoked), scanned A, a copy of folder-structure-blueprint-generator, MIT.

A guide for examining a project's folders and documenting how its files should be organized. It can account for different project types, including .NET, Java, React, Python, Node.js, and Flutter.

In plain words
What is it for?
Use it to create a folder-structure blueprint with naming rules, file-placement patterns, diagrams or tables, file counts, and starter templates.
Why use it?
It gives a team a shared layout for placing files, which reduces confusion as a project grows. A monorepo is a repository containing multiple related projects, and the guide can account for that structure.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create a folder-structure blueprint with naming rules, file-placement patterns, diagrams or tables, file counts, and starter templates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/okhp3/skillz/folder-structure-blueprint-generator
View source ↗ OKHP3/skillz
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 OKHP3/skillz --skill folder-structure-blueprint-generator
Clone the repo
git clone --depth 1 https://github.com/OKHP3/skillz

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.

agentmods badge for folder-structure-blueprint-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/okhp3/skillz/folder-structure-blueprint-generator/github.svg)](https://agentmods.dev/skills/okhp3/skillz/folder-structure-blueprint-generator)
Your own site
<a href="https://agentmods.dev/skills/okhp3/skillz/folder-structure-blueprint-generator"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/folder-structure-blueprint-generator/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 folder-structure-blueprint-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/okhp3/skillz/folder-structure-blueprint-generator"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/folder-structure-blueprint-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,939 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 100% copy Near-identical to another mod 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.00072 $0.02939
Opus 5 $0.00036 $0.01470
Sonnet 5 $0.00014 $0.00588
Haiku 4.5 $0.00007 $0.00294

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

Security

Grade A, and why

folder-structure-blueprint-generator 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 6d 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.

Origin

This is a copy

100% identical to folder-structure-blueprint-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

community/folder-structure-blueprint-generator/SKILL.md · 406 lines

How it starts

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

Project Folder Structure Blueprint Generator

Configuration Variables

${PROJECT_TYPE="Auto-detect|.NET|Java|React|Angular|Python|Node.js|Flutter|Other"}

${INCLUDES_MICROSERVICES="Auto-detect|true|false"}

${INCLUDES_FRONTEND="Auto-detect|true|false"}

${IS_MONOREPO="Auto-detect|true|false"}

${VISUALIZATION_STYLE="ASCII|Markdown List|Table"}

${DEPTH_LEVEL=1-5}

${INCLUDE_FILE_COUNTS=true|false}

${INCLUDE_GENERATED_FOLDERS=true|false}

${INCLUDE_FILE_PATTERNS=true|false}

${INCLUDE_TEMPLATES=true|false}

Generated Prompt

"Analyze the project's folder structure and create a comprehensive 'Project_Folders_Structure_Blueprint.md' document that serves as a definitive guide for maintaining consistent code organization. Use the following approach:

Initial Auto-detection Phase

${PROJECT_TYPE == "Auto-detect" ? "Begin by scanning the folder structure for key files that identify the project type:

  • Look for solution/project files (.sln, .csproj, .fsproj, .vbproj) to identify .NET projects
  • Check for build files (pom.xml, build.gradle, settings.gradle) for Java projects
  • Identify package.json with dependencies for JavaScript/TypeScript projects
  • Look for specific framework files (angular.json, react-scripts entries, next.config.js)
  • Check for Python project identifiers (requirements.txt, setup.py, pyproject.toml)
  • Examine mobile app identifiers (pubspec.yaml, android/ios folders)
  • Note all technology signatures found and their versions" : "Focus analysis on ${PROJECT_TYPE} project structure"}

Read the full file on GitHub · 406 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. 6d ago First seen · 406 lines · 72 tokens per session scan A 6e0c362502ea

Subscribe to this mod's changes

folder-structure-blueprint-generator is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,939 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to folder-structure-blueprint-generator, differing in 0 lines, and is treated as a copy.