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/kunde21/forgejo-mcp/agents-mdgit clone --depth 1 https://github.com/Kunde21/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/kunde21/forgejo-mcp/agents-md)<a href="https://agentmods.dev/instructions/kunde21/forgejo-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kunde21/forgejo-mcp/agents-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.00304 | $0.00304 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
forgejo-mcp AGENTS.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.
What it actually says
Agent Guidelines for forejo-mcp
Build/Test Commands
go build ./...- Build all packagesgo test ./...- Run all tests (includes Forgejo/Gitea integration tests)go test ./path/to/package -run TestName- Run single testgo test -run Integration ./...- Run integration tests onlygo test -v ./...- Run tests with verbose outputgo test -cover ./...- Run tests with coverage reportgo mod tidy- Clean up dependenciesgo vet ./...- Static analysisgoimports -w .- Format code
Code Style Guidelines
- Imports: Use standard library first, then third-party, then local packages with blank lines between groups
- Formatting: Use
goimportsfor consistent formatting - Types: Prefer explicit types; use interfaces for behavior contracts
- Naming: Use camelCase for local variables, PascalCase for exported identifiers
- Error Handling: Always check errors; use
fmt.Errorffor wrapping with context - Documentation: Add godoc comments for all exported functions, types, and constants
- Testing: Use table-driven tests; file names end with
_test.go
Project Structure
- Follow standard Go project layout
- Keep main package in
cmd/directory for executables
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 · 26 lines · 304 tokens per session scan A 26f8f72054f6
forgejo-mcp AGENTS.md is an instructions file published in the GitHub repository Kunde21/forgejo-mcp (5 stars, last pushed 10mo ago), licensed MIT. It adds 304 tokens to every session, about $0.0015 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
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.