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/sakura-byte/discourse-mcp/agents-mdgit clone --depth 1 https://github.com/Sakura-Byte/discourse-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/sakura-byte/discourse-mcp/agents-md)<a href="https://agentmods.dev/instructions/sakura-byte/discourse-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sakura-byte/discourse-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.00785 | $0.00785 |
| Opus 5 | $0.00392 | $0.00392 |
| Sonnet 5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
discourse-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 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.
This is a copy
100% identical to discourse-mcp-extended AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 3d ago First seen · 95 lines · 785 tokens per session scan A 50f9fc125955
discourse-mcp AGENTS.md is an instructions file published in the GitHub repository Sakura-Byte/discourse-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 785 tokens to every session, about $0.0039 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to discourse-mcp-extended AGENTS.md, differing in 0 lines, and is treated as a copy.
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.