Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflownpx agentmods add commands/yassinello/claude-plugin-prd-workflow/generate-claude-mdWrote 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.
[](https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/generate-claude-md)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/generate-claude-md"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/generate-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.
<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/generate-claude-md"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/generate-claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.02376 |
| Opus 5 | $0.00010 | $0.01188 |
| Sonnet 5 | $0.00004 | $0.00475 |
| Haiku 4.5 | $0.00002 | $0.00238 |
Grade A, and why
generate-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate CLAUDE.md Command
Auto-generate a comprehensive CLAUDE.md file that helps Claude Code understand your project.
Purpose
Create a well-structured CLAUDE.md file by automatically detecting:
- Tech stack and framework
- Project structure and patterns
- Development commands
- Code style conventions
- Testing approach
Workflow
Step 1: Analyze Codebase
Detect Tech Stack:
# Check for framework indicators
- package.json → Node.js project
- "next": "14.x" → Next.js 14
- "react": "18.x" → React 18
- "@types/node" → TypeScript
- requirements.txt → Python project
- "fastapi" → FastAPI
- "django" → Django
- Gemfile → Ruby project
- "rails" → Ruby on Rails
- go.mod → Go project
Detect Patterns:
- Directory structure (src/, app/, components/, etc.)
- Testing framework (vitest, jest, pytest, etc.)
- Styling (Tailwind, CSS Modules, styled-components)
- State management (Zustand, Redux, Jotai)
- ORM/Database (Prisma, TypeORM, SQLAlchemy)
Step 2: Extract Development Commands
# From package.json "scripts"
npm run dev → Development server
npm run build → Production build
npm run test → Run tests
npm run lint → Linting
# From Makefile
make dev
make test
# From Justfile
just dev
just build
Step 3: Generate Structured CLAUDE.md
Template Sections:
-
Project Overview
- One-line description
- Tech stack summary
-
Tech Stack
- Framework + version
- Language + version
- Key dependencies
-
Architecture & Patterns
- Architectural pattern (MVC, Clean Architecture, etc.)
- Data flow patterns
- Component structure
-
Directory Structure
- Key directories explained
- File organization conventions
-
Development Commands
- Common commands with descriptions
- Test commands
- Build commands
-
Code Style & Conventions
- Component patterns
- Naming conventions
- Import order
- Formatting rules
-
Testing Approach
- Test framework
- Coverage requirements
- Test file location conventions
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.
- 9d ago First seen · 370 lines · 21 tokens per session scan A 6afcad176999
generate-claude-md is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 21 tokens to every session and 2,376 once invoked, about $0.0001 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-30.
Other commands, from other repositories
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
init
Install the formatters this repository needs, with every command visible before it runs.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.