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 instructions/dwalleck/catalyst/claude-mdgit clone --depth 1 https://github.com/dwalleck/catalystWrote 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/instructions/dwalleck/catalyst/claude-md)<a href="https://agentmods.dev/instructions/dwalleck/catalyst/claude-md"><img src="https://agentmods.dev/badge/instructions/dwalleck/catalyst/claude-md.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.03396 | $0.03396 |
| Opus 5 | $0.01698 | $0.01698 |
| Sonnet 5 | $0.00679 | $0.00679 |
| Haiku 4.5 | $0.00340 | $0.00340 |
Grade C, and why
catalyst CLAUDE.md scanned grade C with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/settings.json | jq . Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la .claude/skills/[skill-name] How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Repository Is
A reference library of Claude Code infrastructure - NOT a working application.
This showcase contains production-tested skills, hooks, agents, and slash commands extracted from 6 months of real-world use managing TypeScript microservices. Users will ask you to help them integrate these components into their own projects.
Critical: When users ask to "add [component]", they mean copy it to THEIR project, not modify this showcase.
Your Role: Integration Assistant
Primary tasks:
- Help users integrate components from this showcase into their projects
- Customize configurations for their specific project structure
- Verify integrations work correctly
- Explain how components function
Before starting ANY integration:
- Read
CLAUDE_INTEGRATION_GUIDE.md- contains detailed integration instructions - Ask about user's project structure
- Verify tech stack compatibility for skills
- Never assume directory structures
Repository Architecture
.claude/
├── skills/ # 5 production skills
│ ├── backend-dev-guidelines/ (Node.js/Express/Prisma)
│ ├── frontend-dev-guidelines/ (React/MUI v7/TanStack)
│ ├── skill-developer/ (Meta-skill, framework-agnostic)
│ ├── route-tester/ (JWT cookie auth testing)
│ ├── error-tracking/ (Sentry integration)
│ └── skill-rules.json (Activation configuration)
├── hooks/ # Rust-based hooks for automation
│ ├── RustHooks/ (Rust implementation)
│ ├── skill-activation-prompt.sh (ESSENTIAL - auto-activates skills)
│ ├── post-tool-use-tracker.sh (ESSENTIAL - tracks file changes)
│ ├── tsc-check.sh (Optional - monorepo TypeScript checks)
│ └── ... (other optional hooks)
├── agents/ # 10 specialized agents (standalone)
│ ├── code-architecture-reviewer.md
│ ├── refactor-planner.md
│ ├── frontend-error-fixer.md
│ └── ... (7 more)
└── commands/ # 3 slash commands
├── dev-docs.md
├── dev-docs-update.md
└── route-research-for-testing.md
dev/
└── README.md # Dev docs pattern documentation
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.
- 4d ago First seen · 489 lines · 3,396 tokens per session scan C fa09a888b28f
catalyst CLAUDE.md is an instructions file published in the GitHub repository dwalleck/catalyst (11 stars, last pushed 9mo ago), licensed MIT. It adds 3,396 tokens to every session, about $0.0170 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.