Worclaude: Instructions file for Claude Code

CLAUDE.md

Worclaude CLAUDE.md is an instructions file for Claude Code from sefaertunc/Worclaude. It costs 2,516 tokens per session, scanned D, original, MIT.

A project instruction file describing Worclaude, a Node.js command-line tool that sets up and maintains a Claude Code workflow.

In plain words
What is it for?
Use it when developing, testing, documenting, or troubleshooting Worclaude and its commands such as initialization, upgrades, status, and diagnostics.
Why use it?
It gives an agent the project's source-of-truth files, technology choices, commands, and known implementation details.

Instructions file for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is sefaertunc/Worclaude's own configuration. It tells Claude Code how to work on Worclaude 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 Worclaude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sefaertunc/Worclaude. 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/sefaertunc/Worclaude/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/sefaertunc/Worclaude

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 Worclaude CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sefaertunc/worclaude/claude-md/github.svg)](https://agentmods.dev/instructions/sefaertunc/worclaude/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/sefaertunc/worclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/sefaertunc/worclaude/claude-md/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 Worclaude CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sefaertunc/worclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/sefaertunc/worclaude/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,516 This file is loaded in full into every session.
When invoked 2,516 The same file — it is already loaded in full.
Security scan D 2 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.02516 $0.02516
Opus 5.5 $0.01006 $0.01006
Sonnet 5.5 $0.00503 $0.00503
Haiku 4.5 $0.00252 $0.00252

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

Security

Grade D, and why

Worclaude CLAUDE.md scanned grade D with 2 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Global npm install requires sudo on some systems — self-update detects EACCES and suggests sudo

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/test-fresh && mkdir /tmp/test-fresh && cd /tmp/test-fresh && git init && node ~/SEFA/GIT/Claude-Workflow/src/index.js init
CLAUDE.md · 160 lines

How it starts

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

CLAUDE.md

worclaude — CLI tool that scaffolds a comprehensive Claude Code workflow into any project.

Key Files

  • docs/spec/PROGRESS.md — Read first every session
  • docs/spec/SPEC.md — Source of truth for all features and design decisions

Tech Stack

  • Runtime: Node.js 20+ (pure ESM, no build step, no transpilation)
  • CLI framework: Commander.js ^14.0.3
  • Interactive prompts: Inquirer.js ^13.4.2 (the list type was renamed to select in v13 — see Gotchas)
  • Terminal styling: Chalk ^5.4.1 (via display.* namespace — never use console.log directly)
  • Spinners: Ora ^9.4.0
  • File operations: fs-extra ^11.3.0
  • Hashing: Node.js crypto (built-in, CRLF-normalized)
  • Testing: Vitest (1011 tests, 71 files)
  • Linting: ESLint flat config (eslint.config.js) + Prettier (single quotes, trailing commas ES5, 100 char width)
  • Docs: VitePress (GitHub Pages via GitHub Actions)
  • Package manager: npm (caret ranges, no lockfile pinning)

Commands

node src/index.js init                # Test init command locally
node src/index.js upgrade             # Test upgrade command
node src/index.js status              # Test status command
node src/index.js doctor              # Test doctor command (workflow health check)
node src/index.js backup              # Test backup command
node src/index.js restore             # Test restore command
node src/index.js diff                # Test diff command
node src/index.js delete              # Test delete command
node src/index.js doc-lint            # Validate `<!-- references … -->` markers and surface tech-stack drift
node src/index.js observability       # Aggregate per-project signals into a Markdown report
node src/index.js regenerate-routing  # Rebuild .claude/skills/agent-routing/SKILL.md from agent files
node src/index.js scan                # Detect project type/stack via project-scanner detectors
node src/index.js setup-state show    # Inspect /setup interview persistence
node src/index.js worktrees clean     # Remove stale agent worktrees
npm test                              # Run tests (1011 tests, 71 files)
npm run lint                          # Lint
npm run format                        # Format
npm run docs:dev                      # VitePress dev server
npm run docs:build                    # Build docs for deployment
/sync                                 # Update PROGRESS.md, SPEC.md, version after merging PRs (run on develop)
/conflict-resolver                    # Resolve merge conflicts (run on develop before /sync)

Read the full file on GitHub · 160 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 · 160 lines · 2,516 tokens per session scan D e3d576563b4f

Subscribe to this mod's changes

Worclaude CLAUDE.md is an instructions file published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 2mo ago), licensed MIT. It adds 2,516 tokens to every session, about $0.0101 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vibetags com-example-config-AsyncTestConfig.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.

PIsberg/vibetags · 82 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,384 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens