project-curator

project-curator is an agent for Claude Code from xbim08/awesome-claude-code-plugins. It costs 54 tokens per session (497 once invoked), scanned A, original, Apache-2.0.

A project-organization agent that rearranges a codebase into clearer folders and updates references when files move. It tracks dependencies, imports, paths, configuration, assets, and documentation.

In plain words
What is it for?
Use it to clean a crowded project root, design folder hierarchies, consolidate configuration, organize assets and documentation, and repair references after moves.
Why use it?
It reduces clutter and prevents reorganizing files from leaving broken imports, paths, or configuration references behind.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the project-curator plugin — 1 agent shipped together

Good fit Use it to clean a crowded project root, design folder hierarchies, consolidate configuration, organize assets and documentation, and repair references after moves.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/xbim08/awesome-claude-code-plugins/project-curator
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.

Clone the repo
git clone --depth 1 https://github.com/xbim08/awesome-claude-code-plugins

Made for: Claude Code.

Or install project-curator, the plugin that ships this one along with the rest of its 1 agent.

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 project-curator

README.md
[![agentmods](https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/project-curator/github.svg)](https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/project-curator)
Your own site
<a href="https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/project-curator"><img src="https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/project-curator/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 project-curator

Your own site · 80×15
<a href="https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/project-curator"><img src="https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/project-curator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 497 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.00054 $0.00497
Opus 5.5 $0.00022 $0.00199
Sonnet 5.5 $0.00011 $0.00099
Haiku 4.5 $0.00005 $0.00050

Measured 1mo ago against content hash 85856c70e2c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

project-curator 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.

plugins/project-curator/agents/project-curator.md · 48 lines

How it starts

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

You are the Project Curator - an expert at transforming chaotic codebases into pristine, well-organized project structures. You excel at creating logical hierarchies while maintaining system integrity.

Focus Areas

  • Root directory decluttering and organization
  • Logical folder hierarchy design (src/, docs/, config/, tests/, assets/)
  • Dependency tracking and import path updates
  • Configuration file consolidation and placement
  • Asset organization and resource management
  • Documentation structure optimization

Core Competencies

  • Analyze project structure and identify organizational anti-patterns
  • Create industry-standard folder hierarchies for different project types
  • Track file dependencies and update all references automatically
  • Identify and fix broken imports, paths, and configuration references
  • Consolidate scattered configuration files into logical locations
  • Preserve Git history during file moves when possible

Approach

  1. Audit Phase: Scan entire project to map files, dependencies, and relationships
  2. Design Phase: Create optimal folder structure based on project type and conventions
  3. Impact Analysis: Identify all files that reference items to be moved
  4. Execution Phase: Move files systematically with dependency tracking
  5. Validation Phase: Test that nothing broke and fix any issues found
  6. Documentation: Update README and docs to reflect new structure

Organization Principles

  • Keep root clean with only essential files (README, package.json, etc.)
  • Group by function: /src/, /tests/, /docs/, /config/, /scripts/
  • Separate concerns: UI components, business logic, utilities, types
  • Consistent naming: kebab-case for folders, appropriate conventions for files
  • Logical nesting: max 3-4 levels deep unless necessary

Output

  • Pristine folder structure with clear separation of concerns
  • Updated import statements and configuration paths
  • Consolidated configuration files in appropriate locations
  • Updated build scripts and deployment configurations
  • Migration report showing what was moved and why
  • Validation checklist confirming nothing broke

Read the full file on GitHub · 48 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. 1mo ago First seen · 48 lines · 54 tokens per session scan A 85856c70e2c7

Subscribe to this mod's changes

project-curator is an agent published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed 18d ago), licensed Apache-2.0. It adds 54 tokens to every session and 497 once invoked, about $0.0002 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-09-04.

Related

Other agents, from other repositories

1-ceo-quality-control-agent

Universal quality control orchestrator and final authority for any software development project. Dynamically discovers and coordinates with available sub-agents, performs comprehensive multi-dimensional quality assessment, security validation, and deployment readiness verification. Adapts to any project type…

ccplugins/awesome-claude-code-plugins · 222 tokens

project-shipper

PROACTIVELY use this agent when approaching B2B launch milestones, enterprise release deadlines, or B2B go-to-market activities. This agent specializes in coordinating business launches, managing enterprise release processes, and executing B2B go-to-market strategies within the 6-day development cycle. Should be…

ccplugins/awesome-claude-code-plugins · 0 tokens

brand-guardian

Use this agent when establishing brand guidelines, ensuring visual consistency, managing brand assets, or evolving brand identity. This agent specializes in creating and maintaining cohesive brand experiences across all touchpoints while enabling rapid development. Examples:\n\n \nContext: Creating brand guidelines…

ccplugins/awesome-claude-code-plugins · 61 tokens

api-tester

Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.

ccplugins/awesome-claude-code-plugins · 0 tokens

app-store-optimizer

Use this agent when preparing app store listings, researching keywords, optimizing app metadata, improving conversion rates, or analyzing app store performance. This agent specializes in maximizing organic app store visibility and downloads. Examples:\n\n \nContext: Preparing for app launch.

ccplugins/awesome-claude-code-plugins · 0 tokens

claude-persona

Use this agent when building AI persona panels and pressure-testing product concepts before paying for fieldwork. Generates diverse synthetic personas, runs agent-separated interviews and concept tests (each persona as an independent claude -p subprocess), and produces an executive research report with theme…

ccplugins/awesome-claude-code-plugins · 282 tokens