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/sqcows/forgejo-mcp/claude-mdgit clone --depth 1 https://github.com/Sqcows/forgejo-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/sqcows/forgejo-mcp/claude-md)<a href="https://agentmods.dev/instructions/sqcows/forgejo-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sqcows/forgejo-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 | $0.01025 | $0.01025 |
| Opus 5 | $0.00513 | $0.00513 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
forgejo-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 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 — 92 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.
Build & Test Commands
npm run build # Compile TypeScript to dist/
npm run dev # Run stdio server (tsx, no build needed)
npm run dev:http # Run HTTP server on port 3000
npm test # Run all 123 tests
npm run test:watch # Watch mode
npx vitest run src/__tests__/tools/repository.test.ts # Run a single test file
npm run lint # ESLint
Architecture
This is an MCP (Model Context Protocol) server for Forgejo/Gitea instances, providing 103 tools across 6 categories. It has two transport modes: stdio (for Claude Code/Desktop) and HTTP (for remote access).
Request Flow
Entry point (index.ts or http.ts)
→ config.ts (loads env vars / CLI args, validates URL for SSRF)
→ server.ts (creates McpServer, registers all tool groups)
→ tools/*.ts (each tool calls ForgejoClient methods)
→ client.ts (wraps fetch with token auth, hits /api/v1)
Key Modules
server.ts— Factory that createsMcpServerand calls sixregister*Tools()functionsclient.ts—ForgejoClientclass withget/post/patch/put/delete/getRawmethods. Errors are wrapped inForgejoApiErrorwith sanitized URLs (no token leakage)config.ts—resolveConfig()merges CLI args > env vars > defaults.validateBaseUrl()blocks SSRF (cloud metadata IPs, private ranges)validation.ts— Centralized Zod schemas (zOwner,zRepo,zFilePath,zPage,zLimit, etc.) shared across all tool filestools/helpers.ts—formatResponse(data)andformatError(err)produce the MCP content formathttp.ts— HTTP transport withRateLimiterclass, optional Bearer auth (FORGEJO_MCP_API_KEY), security headers,/healthendpoint
Tool Registration Pattern
Every tool file exports a single register*Tools(server, client) function. Each tool follows this structure:
server.tool(
"tool_name", // snake_case identifier
"Description", // shown in MCP UI
{ owner: zOwner, repo: zRepo, ...params }, // Zod schemas (raw shape, NOT wrapped in z.object)
async (params) => {
const { owner, repo, ...query } = params;
const result = await client.get(`/repos/${owner}/${repo}`, query);
return formatResponse(result);
}
);
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 · 92 lines · 1,025 tokens per session scan A b328b133c623
forgejo-mcp CLAUDE.md is an instructions file published in the GitHub repository Sqcows/forgejo-mcp (10 stars, last pushed 2mo ago), licensed MIT. It adds 1,025 tokens to every session, about $0.0051 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
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.
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).
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.
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).