claude-organizer: Command for Claude Code

.claude/commands/claude-organize-js.md

claude-organize-js is a command for Claude Code from ramakay/claude-organizer. It costs 0 tokens per session (482 once invoked), scanned A, original, MIT.

A command for organizing standalone JavaScript and MJS utility files in a project. It offers a conservative mode and an experimental, more aggressive mode, with warnings and confirmation first.

In plain words
What is it for?
Use it to sort files such as checks, tests, debugging tools, command-line scripts, and data generators. It is intended for projects where these files need a safer, more consistent layout.
Why use it?
It helps tidy utility scripts while reducing the risk of moving source files, configuration, exports, or application entry points. JavaScript organization is disabled by default because changing file locations can break projects.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is ramakay/claude-organizer's own configuration. It tells Claude Code how to work on claude-organizer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-organizer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ramakay/claude-organizer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ramakay/claude-organizer/main/.claude/commands/claude-organize-js.md
Clone the repo
git clone --depth 1 https://github.com/ramakay/claude-organizer

Made for: Claude Code.

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 claude-organize-js

README.md
[![agentmods](https://agentmods.dev/badge/commands/ramakay/claude-organizer/claude-organize-js/github.svg)](https://agentmods.dev/commands/ramakay/claude-organizer/claude-organize-js)
Your own site
<a href="https://agentmods.dev/commands/ramakay/claude-organizer/claude-organize-js"><img src="https://agentmods.dev/badge/commands/ramakay/claude-organizer/claude-organize-js/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 claude-organize-js

Your own site · 80×15
<a href="https://agentmods.dev/commands/ramakay/claude-organizer/claude-organize-js"><img src="https://agentmods.dev/badge/commands/ramakay/claude-organizer/claude-organize-js.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 482 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.00000 $0.00482
Opus 5 $0.00000 $0.00241
Sonnet 5 $0.00000 $0.00096
Haiku 4.5 $0.00000 $0.00048

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

Security

Grade A, and why

claude-organize-js 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 11d 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/commands/claude-organize-js.md · 84 lines

How it starts

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

Enable JavaScript/MJS Organization (Experimental)

⚠️ WARNING: EXPERIMENTAL FEATURE

This command enables JavaScript/MJS file organization, which is DISABLED by default for safety reasons.

What This Command Does

When you run this command, Claude Organize will:

  1. Show you important warnings about the risks
  2. Ask for confirmation before enabling
  3. Let you choose between 'safe' and 'aggressive' modes
  4. Enable JS organization for your current project

Safety Considerations

Files That WILL Be Organized:

  • Utility scripts like check-*.js, test-*.js, debug-*.js
  • Standalone scripts with no exports
  • CLI tools with shebang lines
  • Test data generators and debugging utilities

Files That Will NEVER Be Touched:

  • ❌ Any file in src/, lib/, dist/, build/
  • ❌ Files with export or module.exports
  • ❌ React/Vue/Angular components
  • ❌ Config files (*.config.js)
  • ❌ Package entry points (index.js, main.js)

Modes Available

Safe Mode (Recommended)

  • Only organizes files matching known utility patterns
  • Most conservative approach
  • Pattern-based detection only

Aggressive Mode

  • Uses AI analysis with 95% confidence requirement
  • Can detect more utility scripts
  • Higher risk of false positives

Before Enabling

CRITICAL CHECKLIST:

  • Your project is under version control (Git)
  • You have committed all changes
  • You have tested on a non-critical project first
  • You understand the risks involved
  • You will monitor the organization log

How to Use

Simply type:

/claude-organize-js

Claude will guide you through the process with appropriate warnings and confirmations.

To Disable

If you need to disable JS organization:

unset CLAUDE_ORGANIZE_JS

Or in your .env file:

CLAUDE_ORGANIZE_JS=false

Remember

This feature is experimental. Even with all safety measures, there's always a risk when moving JavaScript files. Use with extreme caution and always have backups!

Read the full file on GitHub · 84 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. 11d ago First seen · 84 lines · 0 tokens per session scan A c33238c43dcb

Subscribe to this mod's changes

claude-organize-js is a command published in the GitHub repository ramakay/claude-organizer (68 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 tokens. 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.