Borrowing it
Nothing to install: this file belongs to tyler-technologies-oss/forge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tyler-technologies-oss/forge-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/tyler-technologies-oss/forge-mcpWrote 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/tyler-technologies-oss/forge-mcp/claude-md)<a href="https://agentmods.dev/instructions/tyler-technologies-oss/forge-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/tyler-technologies-oss/forge-mcp/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.1 | $0.00524 | $0.00524 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
forge-mcp 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 3d 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 — 61 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.
Commands
Development Workflow
pnpm install- Install dependenciespnpm run build- Compile TypeScript to dist/ and bundle manifests
Code Quality
pnpm run lint- Run ESLint to check code qualitypnpm run format- Format code with Prettierpnpm run format:check- Check if code is properly formatted
Testing
pnpm test- Run all testspnpm test:watch- Run tests in watch modepnpm test:coverage- Run tests with coverage report
Versioning & Release
When releasing a new version, update the version number in all three files:
package.jsonplugin/.claude-plugin/plugin.json.claude-plugin/marketplace.json
Data Flow
- Server initialization loads CEM data from filesystem
- Optimized Resource Listing: Returns streamlined set of 8 core resources plus individual components
- Consolidated Resource Reading: Generates markdown documentation with intelligent consolidation
- Tool-Based Granular Access: Tools provide filtered access to specific sections when needed
Key Patterns
- Singleton Services: All services (ResourceManager, CEMLoader, TemplateEngine) use singleton pattern
- Async Initialization: ResourceManager.initialize() must be called before use
- URI Validation: All resource URIs validated before processing
TypeScript Configuration
- ES modules (
"type": "module"in package.json) - Compiled output goes to
dist/ - Uses
.jsextensions in imports for ES module compatibility
Resource Templates
Templates are located in the /templates/ directory, and written in markdown with optional Handlebars syntax.
Guidelines for Claude
When suggesting code changes or additions, please adhere to the following guidelines:
- DO NOT run the debug command to test changes, only run the build command.
- Always use pnpm to run commands. DO NOT use npm or pntml
- DO NOT generate fallback content for tools unless instructed otherwise.
- ALWAYS run pnpm format before finalizing changes to ensure consistent formatting.
- When renaming tools or resources, ensure all references are updated accordingly.
- Avoid introducing new dependencies unless absolutely necessary.
- Avoid rendering markdown directly in the code unless its small snippets. Prefer templates instead.
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.
- 3d ago Changed · +12 lines · +90 tokens per session 0c4312620663
- 7d ago First seen · 49 lines · 434 tokens per session scan A 1108d0c9d4d5
forge-mcp CLAUDE.md is an instructions file published in the GitHub repository tyler-technologies-oss/forge-mcp (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 524 tokens to every session, about $0.0026 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
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.