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.
npx agentmods add commands/sgaunet/claude-plugins/gen-claudegit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/gen-claude)<a href="https://agentmods.dev/commands/sgaunet/claude-plugins/gen-claude"><img src="https://agentmods.dev/badge/commands/sgaunet/claude-plugins/gen-claude.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.06129 |
| Opus 5 | $0.00010 | $0.03064 |
| Sonnet 5 | $0.00004 | $0.01226 |
| Haiku 4.5 | $0.00002 | $0.00613 |
Grade A, and why
gen-claude 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 5d 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 — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate CLAUDE.md Command
Automatically generate or enhance a project-specific CLAUDE.md file following 2025-2026 best practices. This command performs deep codebase analysis to create comprehensive project documentation that stays within the 2500 token limit.
Why This Command Exists
Problem: Projects often lack CLAUDE.md files or have poorly structured ones, forcing Claude to operate without project-specific context.
Solution: Automated generation that:
- Analyzes codebase comprehensively
- Auto-detects linter/formatter configs (avoids duplication)
- Creates docs/ folder for progressive disclosure
- Merges/enhances existing CLAUDE.md (preserves customizations)
- Optimizes for 2500 token limit
Content Generation Rules
CRITICAL: When generating any content (CLAUDE.md, docs/, commit messages, descriptions, or any other output):
- NEVER add Claude Code attribution or co-authorship
- NEVER include phrases like "Generated by Claude", "Created with Claude Code", or similar
- NEVER add "Co-Authored-By: Claude" in commit messages or documentation
- All generated content should appear as if written by a human developer
- Focus on technical accuracy and project-specific details, not tool attribution
Process (5 Phases)
Phase 1: Parallel Discovery (4 Sonnet Agents)
Launch 4 independent agents concurrently to analyze different aspects of the project:
Agent #1: Project Structure Analyzer
Task(subagent_type: "Explore", model: "sonnet", prompt: "
Analyze project structure and return JSON:
{
languages: [list of detected languages from file extensions],
frameworks: [frameworks/libraries detected from imports/configs],
buildTool: string (npm/go/cargo/maven/gradle/make/task/etc),
buildCommands: {build: '', test: '', lint: '', run: ''},
structure: {
source: path,
tests: path,
docs: path,
config: path
}
}
Detection strategy:
- Languages: Glob for *.go, *.js, *.py, *.rs, *.java, *.rb, *.php
- Build tools: Look for package.json, go.mod, Cargo.toml, requirements.txt, pom.xml, build.gradle, Makefile, Taskfile.yml
- Extract commands from: npm scripts, Makefile targets, Taskfile tasks, go.mod for go commands
- Map directory structure: src/, test/, docs/, internal/, cmd/, pkg/
")
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.
- 5d ago First seen · 631 lines · 19 tokens per session scan A 0413ddd25886
gen-claude is a command published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 6,129 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
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.