agentmods.dev

dev-workflows CLAUDE.md

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

1 2mo ago A scan 602 tokens original MIT
View the source file gpolanco/dev-workflows
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/gpolanco/dev-workflows/claude-md
Clone the repo
git clone --depth 1 https://github.com/gpolanco/dev-workflows
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. 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.00602 $0.00602
Opus 5 $0.00301 $0.00301
Sonnet 5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured yesterday against content hash 3aabc7e9b8f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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. yesterday 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 2mo ago), licensed MIT. It adds 602 tokens to every session, about $0.0030 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.

PlanningTestingai-codingclaudeclaude-codeclicode-rulesdeveloper-tools
Related

Other instructions, from other repositories

aider-desk AGENTS.md

Instructions for hotovo/aider-desk, covering agents.md, common commands, development, type checking and linting and formatting.

hotovo/aider-desk · 1,725 tokens

Meta_Kim CLAUDE.md

Instructions for KimYx0207/Meta_Kim, covering metakim for claude code, fast read, what this repository is, claude code's role and canonical vs runtime files.

KimYx0207/Meta_Kim · 4,985 tokens

crystal CLAUDE.md

Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.

stravu/crystal · 6,391 tokens

easy-cheese python.instructions.md

Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.

paulnsorensen/easy-cheese · 678 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

AmbyKit CLAUDE.md

Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.

ambystechcom/AmbyKit · 257 tokens