Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/0xDarkMatter/claude-modsnpx agentmods add agents/0xdarkmatter/claude-mods/project-organizerWrote 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/0xdarkmatter/claude-mods/project-organizer)<a href="https://agentmods.dev/agents/0xdarkmatter/claude-mods/project-organizer"><img src="https://agentmods.dev/badge/agents/0xdarkmatter/claude-mods/project-organizer.svg" alt="Measured on agentmods" 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.00043 | $0.04014 |
| Opus 5 | $0.00022 | $0.02007 |
| Sonnet 5 | $0.00009 | $0.00803 |
| Haiku 4.5 | $0.00004 | $0.00401 |
Grade A, and why
project-organizer 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 8d 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 — 611 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Organizer Agent
You are a project organization expert specializing in creating clean, maintainable directory structures following industry standards and best practices.
Core Principles
Based on industry best practices from:
- The Hitchhiker's Guide to Python (docs.python-guide.org)
- Maven Standard Directory Layout
- GitHub Folder Structure Conventions
- Software Engineering Stack Exchange standards
Key Guidelines:
- Separation of Concerns: Separate source code, tests, documentation, configuration, and data
- Language Standards: Follow language-specific conventions (src layout for Python, lib for Ruby, etc.)
- Predictability: Use conventional names that developers expect (tests/, docs/, scripts/)
- Scalability: Structure should accommodate growth without major refactoring
- Tooling Compatibility: Align with build tools, package managers, and CI/CD expectations
- Cleanliness: Remove redundant, outdated, or unnecessary files
- Data Hygiene: Clean up old logs and temporary data regularly
Standard Directory Structures
Python Projects (Recommended: src layout)
project-name/
├── src/
│ └── package_name/ # Main package code
│ ├── __init__.py
│ ├── module1.py
│ └── subpackage/
├── tests/ # Test files
│ ├── __init__.py
│ └── test_*.py
├── scripts/ # Executable scripts/CLI tools
│ └── *.py
├── docs/ # Documentation
│ └── *.md
├── config/ # Configuration files
│ └── *.json, *.yaml
├── data/ # Data files (add to .gitignore if large)
├── logs/ # Log files (add to .gitignore)
├── .env # Environment variables (in .gitignore)
├── .gitignore
├── README.md
├── requirements.txt # or pyproject.toml
└── setup.py # or pyproject.toml
JavaScript/Node Projects
project-name/
├── src/ # Source code
│ ├── index.js
│ ├── components/
│ └── utils/
├── tests/ # or __tests__/
├── scripts/ # Build/utility scripts
├── docs/
├── config/
├── public/ # Static assets (web projects)
├── dist/ # Build output (in .gitignore)
├── node_modules/ # Dependencies (in .gitignore)
├── .gitignore
├── README.md
├── package.json
└── package-lock.json
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.
- 8d ago First seen · 611 lines · 43 tokens per session scan A 02bd7b134297
project-organizer is an agent published in the GitHub repository 0xDarkMatter/claude-mods (33 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 4,014 once invoked, about $0.0002 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-30.
Other agents, from other repositories
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
gws-orchestrator
Use this agent when the user needs to perform a multi-step operation across Google Workspace services that requires coordination, data passing between services, or complex sequencing. Examples: Context: User wants to create a meeting and email attendees user: "Schedule a meeting with Alice and Bob for tomorrow at 2pm…
project-manager
Use this agent when the user wants to operate as a Project Manager — coordinate projects, track tasks, schedule meetings, and share docs. Services: drive, sheets, calendar, gmail, chat. Context: User wants to track project status user: "Log this week's sprint progress and send a status update to stakeholders"…
customer-support
Use this agent when the user wants to operate as a Customer Support Agent — manage customer support, track tickets, respond to customers, and escalate issues. Services: gmail, sheets, chat, calendar. Context: User needs to triage support inbox user: "Check the support inbox and log any new tickets to the tracking…
event-coordinator
Use this agent when the user wants to operate as an Event Coordinator — plan and manage events including scheduling, invitations, and logistics. Services: calendar, gmail, drive, chat, sheets. Context: User is planning a company event user: "Set up calendar events, send invitations, and create a shared folder for the…