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/rubencodeforges/codeforges-claude-plugin/claude-mdgit clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-pluginWrote 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/rubencodeforges/codeforges-claude-plugin/claude-md)<a href="https://agentmods.dev/instructions/rubencodeforges/codeforges-claude-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/rubencodeforges/codeforges-claude-plugin/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.02014 | $0.02014 |
| Opus 5 | $0.01007 | $0.01007 |
| Sonnet 5 | $0.00403 | $0.00403 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
codeforges-claude-plugin 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 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.
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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugin Development Guide
This file contains instructions for Claude Code when working on this plugin.
Plugin Purpose
cf-dev-toolkit is a daily development workflow plugin that solves Claude Code's tendency to:
- Read only 20-30 lines and miss context
- Lose focus on complex tasks
- Make assumptions about method signatures
- Get overwhelmed by real-world development work
It provides specialized sub-agents with separate context windows that stay focused, understand complete context, and verify before suggesting code.
Important Rules
When Modifying Agents
-
Keep Proactive Keywords
- Always include
MUST BE USEDandUSE PROACTIVELYin descriptions - These trigger automatic invocation based on user's natural language
- Always include
-
Verification First
- All agents must check actual method signatures before suggesting code
- No assumptions - always read implementations
-
Smart Reading Strategy
- Files < 1000 lines: Read completely
- Files > 1000 lines: Strategic reading (imports, exports, key sections) + Grep
- Never say "I only read X lines" without justification
-
No Hard-Coded Numbers
- Don't mention "7 agents" or "3 skills" in descriptions
- Plugin may grow - keep descriptions version-agnostic
File Structure
cf-dev-toolkit/
├── .claude-plugin/
│ └── marketplace.json # Marketplace config (name, owner, plugins)
├── manifest.json # Plugin manifest (agents, skills, commands)
├── agents/ # Sub-agent definitions (.md files)
├── skills/ # Auto-loading knowledge (.md files)
├── commands/ # Slash commands (.md files)
├── LICENSE # MIT license
├── .gitignore # Git exclusions
├── CONTRIBUTING.md # Contribution guidelines
├── README.md # User-facing documentation
└── CLAUDE.md # This file (for Claude Code)
Naming Conventions
- Plugin name:
cf-dev-toolkit(not "code-analysis-toolkit") - Author:
codeforges(orcffor short) - Owner:
codeforgesin marketplace.json
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 · 278 lines · 2,014 tokens per session scan A 3da144ebbace
codeforges-claude-plugin CLAUDE.md is an instructions file published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (2 stars, last pushed 9mo ago), licensed MIT. It adds 2,014 tokens to every session, about $0.0101 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.
Other instructions, from other repositories
aider-desk AGENTS.md
AGENTS.md instructions for hotovo/aider-desk, covering agents.md, common commands, development, type checking and linting and formatting.
muggle-ai-teams CLAUDE.md
Instructions for multiplex-ai/muggle-ai-teams, covering claude.md, what this repo is, installation & setup, option a: npm (copies files to /.claude/) and option b: git clone (symlinks to /.claude/).
claude-setup CLAUDE.md
Instructions for stuartshields/claude-setup, covering global protocol (v2026.2), 0. shortcuts & triggers, 1. mandatory workflow, 2. dynamic project initialization / migration and 3. agent routing.
.agents AGENTS.md
AGENTS.md instructions for Weaverse/.agents, covering agent guidelines for .agents, repository structure, build, lint & test commands, validation commands and validate json configuration.
LLM-Autonomous-Agent-Plugin-for-Claude CLAUDE.md
Claude Code instructions for bejranonda/LLM-Autonomous-Agent-Plugin-for-Claude, covering claude.md, project overview, development guidelines, ⚠️ critical: cross-platform encoding guidelines and 🏗️ development & distribution architecture.
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).