Borrowing it
Nothing to install: this file belongs to devzspy/discourse-mcp-extended. 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/devzspy/discourse-mcp-extended/main/AGENTS.mdgit clone --depth 1 https://github.com/devzspy/discourse-mcp-extendedWrote 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/devzspy/discourse-mcp-extended/agents-md)<a href="https://agentmods.dev/instructions/devzspy/discourse-mcp-extended/agents-md"><img src="https://agentmods.dev/badge/instructions/devzspy/discourse-mcp-extended/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/devzspy/discourse-mcp-extended/agents-md"><img src="https://agentmods.dev/badge/instructions/devzspy/discourse-mcp-extended/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00785 | $0.00785 |
| Opus 5.5 | $0.00314 | $0.00314 |
| Sonnet 5.5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
discourse-mcp-extended 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- discourse-mcp AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Discourse MCP
MCP server exposing Discourse forum capabilities as tools/resources for AI agents.
Entry: src/index.ts → dist/index.js (binary: discourse-mcp). Node >= 24.
SDLC Commands
pnpm build # Compile TypeScript to dist/
pnpm typecheck # Type-check only (no emit)
pnpm lint # Run ESLint on src/
pnpm test # Run tests (requires build first)
pnpm clean # Remove dist/
Source Map
| Area | Files |
|---|---|
| Entry/CLI | src/index.ts |
| HTTP client | src/http/client.ts |
| Tool registry | src/tools/registry.ts |
| Resource registry | src/resources/registry.ts |
| Built-in tools | src/tools/builtin/* |
| Remote tools | src/tools/remote/tool_exec_api.ts |
| Utilities | src/util/*.ts (logger, redact, json_response) |
Key Patterns
Tool Implementation
- Tools live in
src/tools/builtin/as individual files - Each tool exports a registration function called by
src/tools/registry.ts - All tools return strict JSON (no Markdown) with
isError: trueon failure - Write tools require
--allow_writesflag and matchingauth_pairsentry
Resources
- URI-addressable read-only data (categories, tags, groups, channels, drafts)
- Registered in
src/resources/registry.ts
HTTP Layer
- Client in
src/http/client.tshandles auth, retries (429/5xx), caching - User-Agent:
Discourse-MCP/0.x - Write tools enforce ~1 req/sec rate limit
Configuration
- CLI flags validated via Zod in
src/index.ts - Auth via
--auth_pairsJSON (API keys or User API keys) --site <url>tethers to single site, hidesdiscourse_select_sitetool
Testing
- Tests in
src/test/use Node's built-in test runner - Build before running tests:
pnpm build && pnpm test
Adding a New Tool
- Create
src/tools/builtin/<name>.ts - Export a
RegisterFnfunction - Import and call it in
src/tools/registry.ts
Minimal template:
import { z } from "zod";
import type { RegisterFn } from "../types.js";
import { jsonResponse, jsonError } from "../../util/json_response.js";
export const registerMyTool: RegisterFn = (server, ctx, opts) => {
if (!opts.allowWrites) return; // omit for read-only tools
server.registerTool(
"discourse_my_tool",
{
title: "My Tool",
description: "Does X. Returns JSON with Y.",
inputSchema: z.object({ id: z.number() }).shape,
},
async (args) => {
const { client } = ctx.siteState.ensureSelectedSite();
try {
const data = await client.get(`/endpoint.json`);
return jsonResponse(data);
} catch (e: any) {
return jsonError(`Failed: ${e?.message}`);
}
}
);
};
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.
- 2mo ago First seen · 95 lines · 785 tokens per session scan A 50f9fc125955
discourse-mcp-extended AGENTS.md is an instructions file published in the GitHub repository devzspy/discourse-mcp-extended (0 stars, last pushed 3mo ago), licensed MIT. It adds 785 tokens to every session, about $0.0031 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.