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/raohwork/forgejo-mcp/claude-mdgit clone --depth 1 https://github.com/raohwork/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/raohwork/forgejo-mcp/claude-md)<a href="https://agentmods.dev/instructions/raohwork/forgejo-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/raohwork/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.01480 | $0.01480 |
| Opus 5 | $0.00740 | $0.00740 |
| Sonnet 5 | $0.00296 | $0.00296 |
| Haiku 4.5 | $0.00148 | $0.00148 |
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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forgejo MCP Server
A Model Context Protocol (MCP) server that enables MCP clients to interact with Gitea/Forgejo repositories.
Project Overview
This project provides MCP integration for managing Forgejo/Gitea repositories through MCP-compatible clients such as Claude Desktop, Continue, and other LLM applications.
Supported Operations
- Issues (create, edit, comment, close)
- Labels (list, create, edit, delete)
- Milestones (list, create, edit, delete)
- Releases (list, create, edit, delete, manage assets)
- Pull requests (list, view)
- Repository search and listing
- Wiki pages (create, edit, delete)
- Forgejo Actions tasks (view)
Transport Modes
- stdio: Standard input/output (best for local integration)
- sse: Server-Sent Events over HTTP (best for web apps) - planned
- http: HTTP POST requests (best for simple integrations) - planned
Architecture
Core Components
- cmd/: CLI application using Cobra framework
root.go: Main command with global configurationstdio.go: Stdio transport mode implementation
- types/: Data structures and response types
api.go: MCP response types wrapping Forgejo SDK types
- main.go: Application entry point
Key Dependencies
- MCP SDK:
github.com/modelcontextprotocol/go-sdk- There are 3 important sub packages:
mcp,jsonschemaandjsonrpc
- There are 3 important sub packages:
- Forgejo SDK:
codeberg.org/mvdkleijn/forgejo-sdk/forgejo/v2 - CLI Framework:
github.com/spf13/cobra - Configuration:
github.com/spf13/viper
If you need to get documentation of these packages, go doc should be the best bet.
Implementation Strategy
- 🟢 SDK-based (71%): Use official Forgejo SDK where available
- 🟡 Custom HTTP (29%): Implement custom requests for unsupported features (Wiki, Actions, Issue dependencies)
Configuration
CLI Arguments
forgejo-mcp stdio --server https://git.example.com --token your_token
Environment Variables
FORGEJOMCP_SERVER: Forgejo server URLFORGEJOMCP_TOKEN: Access token
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 · 182 lines · 1,480 tokens per session scan A 870a92299abf
forgejo-mcp CLAUDE.md is an instructions file published in the GitHub repository raohwork/forgejo-mcp (67 stars, last pushed 10mo ago), licensed MPL-2.0. It adds 1,480 tokens to every session, about $0.0074 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 instructions, from other repositories
gitea-mcp-server AGENTS.md
AGENTS.md instructions for pxsloot/gitea-mcp-server, covering agent guidelines, what we build, developer handbook and fastmcp documentation.
gimp-mcp CLAUDE.md
Claude Code instructions for maorcc/gimp-mcp, covering claude.md, architecture, installation & setup, gimp plugin installation and mcp server configuration.
MCP_Pokemon GEMINI.md
Gemini CLI instructions for Asthanaji05/MCP_Pokemon, covering gemini's scratchpad, project context, current task and agent directives.
linkedin-mcp-server AGENTS.md
AGENTS.md instructions for stickerdaniel/linkedin-mcp-server, covering claude.md, development commands, scraping rules, browser identity rules and profile safety rules.
pagespeed-insights-mcp AGENTS.md
AGENTS.md instructions for ruslanlap/pagespeed-insights-mcp, covering project rules — pagespeed-insights-mcp (mcp server), специфіка проєкту, обов'язкові практики (mcp + ts), serena + .serena/ and професійні skills тільки.
kafka-schema-reg-mcp AGENTS.md
AGENTS.md instructions for aywengo/kafka-schema-reg-mcp, covering development guidelines, prerequisites, quick setup, install dependencies and install dev dependencies (optional but recommended).