agentmods.dev

dev-workflows: Instructions file for Claude Code

CLAUDE.md

dev-workflows CLAUDE.md is an instructions file for Claude Code from gpolanco/dev-workflows. It costs 602 tokens per session, scanned A, original, MIT.

Instructions for working on the dev-workflows project, including its development process, technology choices, architecture, commands, and specifications.

In plain words
What is it for?
Use them when implementing features, running tests or builds, and working with the project's command-line tool and rule files.
Why use it?
They give an agent the project context it needs before making changes, reducing the chance of breaking established patterns.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Gemini CLI.

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

not rated 1repo 4mo ago A scan 602 tokens original MIT
View source ↗ gpolanco/dev-workflows npmjs.com
Reuse

Borrowing it

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

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 dev-workflows CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gpolanco/dev-workflows/claude-md"><img src="https://agentmods.dev/badge/instructions/gpolanco/dev-workflows/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 602 This file is loaded in full into every session.
When invoked 602 The same file — it is already loaded in full.
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.00602 $0.00602
Opus 5.5 $0.00241 $0.00241
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

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

Security

Grade A, and why

dev-workflows CLAUDE.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 2mo 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.md · 58 lines

How it starts

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

Dev Workflows

CLI tool that compiles developer rules into editor-specific config files (CLAUDE.md, .cursor/rules, GEMINI.md).

Stack

  • Monorepo with pnpm workspaces
  • CLI in packages/cli/ (TypeScript, commander)
  • Rules in content/rules/ (Markdown with YAML frontmatter, hosted on GitHub)
  • Tests with node:test

Architecture

  • content/rules/ → official rule files (Markdown), fetched from GitHub via devw add
  • content/blocks/ → local prebuilt blocks installed via devw add <block-id>
  • packages/cli/src/bridges/ → per-tool adapters that translate rules → native format
  • Bridges only translate. They do not add new intent or logic.

Key commands

pnpm install                    # install deps
pnpm build                      # build CLI
pnpm test                       # run tests
pnpm dev                        # dev mode
devw add                        # interactive: browse and install rules from registry
devw add typescript/strict      # direct: install specific rule
devw add --list                 # list available rules

Specs (read before implementing)

  • openspec/specs/cli/spec.md → CLI spec (commands, bridges, UI, registry) — current state
  • openspec/specs/decisions/spec.md → accepted decisions (source of truth if conflict)
  • openspec/specs/docs/spec.md → Mintlify documentation site spec
  • openspec/specs/theme/spec.md → design system for the landing page
  • openspec/changes/pull-command/tasks.md → feat/pull-command branch state (pending merge)
  • openspec/ is gitignored — internal specs not published

If a decision is not in the specs, do not implement it. Propose a documentation change first.

Git workflow (BLOCKING — do this BEFORE writing any code)

  1. NEVER commit directly to main. Always create a feature branch first.
  2. Branch naming: feat/<slug>, fix/<slug>, chore/<slug>, docs/<slug>
  3. Commits: feat(scope): ..., fix(scope): ..., docs(scope): ..., chore(scope): ...
  4. Don't create PRs without my approval.
  5. One PR per feature. Include: what/why, list of changes, how to test.
  6. Clean up branch after merge.

Read the full file on GitHub · 58 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. 2mo ago First seen · 58 lines · 602 tokens per session scan A 3aabc7e9b8f4

Subscribe to this mod's changes

dev-workflows CLAUDE.md is an instructions file published in the GitHub repository gpolanco/dev-workflows (1 stars, last pushed 4mo ago), licensed MIT. It adds 602 tokens to every session, about $0.0024 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-08-31.

Claude Codeai-codingclaudeclicode-rulesdeveloper-tools
Related

Other instructions, from other repositories

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,715 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,461 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,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens