agentmods.dev

Worclaude AGENTS.md

Worclaude AGENTS.md is an instructions file for Codex, OpenCode from sefaertunc/Worclaude. It costs 507 tokens per session, scanned A, original, MIT.

A project guide for Worclaude, a CLI tool that sets up and manages a Claude Code workflow in a project. It documents the required Node.js version, commands, code conventions, and folder structure.

In plain words
What is it for?
Use it when developing, testing, formatting, documenting, or extending Worclaude, especially its CLI commands and core workflow files.
Why use it?
It gives contributors a shared reference for running tests, linting, formatting, building documentation, and using the CLI consistently. It also highlights rules such as using named exports and avoiding direct console output.

Instructions file for CodexOpenCode

not rated 4 25d ago A scan 507 tokens original MIT
View the source file sefaertunc/Worclaude
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.

agentmods
npx agentmods add instructions/sefaertunc/worclaude/agents-md
Clone the repo
git clone --depth 1 https://github.com/sefaertunc/Worclaude

Made for: Codex, OpenCode.

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 AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sefaertunc/worclaude/agents-md.svg)](https://agentmods.dev/instructions/sefaertunc/worclaude/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/sefaertunc/worclaude/agents-md"><img src="https://agentmods.dev/badge/instructions/sefaertunc/worclaude/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 507 This file is loaded in full into every session.
When invoked 507 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00507 $0.00507
Opus 5 $0.00253 $0.00253
Sonnet 5 $0.00101 $0.00101
Haiku 4.5 $0.00051 $0.00051

Measured 4d ago against content hash b75b97507850, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Worclaude AGENTS.md 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 4d 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.

AGENTS.md · 52 lines

How it starts

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

AGENTS.md

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

Tech Stack

  • Node.js 20+ (pure ESM, no build step)
  • Commander.js, Inquirer.js, Chalk, Ora, fs-extra
  • Vitest (1011 tests, 71 files)
  • ESLint flat config + Prettier
  • VitePress for docs

Build & Test Commands

npm test                        # Run tests
npm run lint                    # Lint
npm run format                  # Format
npm run docs:build              # Build VitePress docs
node src/index.js <command>     # Test a CLI command locally

Code Conventions

  • Named exports only (no default exports).
  • Use display.* helpers for user output — never console.log.
  • Operate on parsed JSON objects; never text-substitute on stringified JSON.
  • Cross-platform: path.join, os.platform(), never hardcode separators.
  • Read source files before modifying them. Ask if ambiguous, do not guess.

Project Structure

  • src/commands/ — CLI command handlers (init, upgrade, status, doctor, backup, restore, diff, delete, doc-lint, observability, regenerate-routing, scan, setup-state, worktrees)
  • src/core/ — config, merger, scaffolder, workflow-meta
  • src/data/ — agent catalogs, stack definitions, routing metadata
  • src/generators/ — dynamic file generators (agent-routing.md, etc.)
  • src/utils/ — display, npm helpers, hashing
  • templates/ — user-facing scaffold content (agents, commands, skills, hooks, settings)
  • docs/spec/ — SPEC.md (source of truth) and PROGRESS.md (read first every session)

Key Principles

  • Source of truth: docs/spec/SPEC.md. Features must match the spec exactly.
  • One feature at a time. Test after each. Commit working increments.
  • Every merge to main gets at least a patch version bump (even docs/CI/test-only).
  • Feature branches never modify shared-state files — those are updated on develop via /sync after merging PRs.
  • Never add Co-Authored-By trailers or AI attribution to commits/PRs.

Read the full file on GitHub · 52 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. 4d ago First seen · 52 lines · 507 tokens per session scan A b75b97507850

Subscribe to this mod's changes

Worclaude AGENTS.md is an instructions file published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 25d ago), licensed MIT. It adds 507 tokens to every session, about $0.0025 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-31.

Testingaiai-agentai-agentsai-toolsautomationclaude
Related

Other instructions, from other repositories

ai-workflow AGENTS.md

Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.

cunhaax/ai-workflow · 2,602 tokens

trackly-cli CLAUDE.md

Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.

trackly-app/trackly-cli · 3,195 tokens

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

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

PIsberg/vibetags · 82 tokens

pupila CLAUDE.md

Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.

FranRom/pupila · 4,040 tokens

claude-bridge AGENTS.md

Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.

kadaba/claude-bridge · 1,505 tokens

McpServer AGENTS.md

AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.

sharpninja/McpServer · 1,993 tokens