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 skills add jrmatherly/mcp-context-forge --skill mcf-plugingit clone --depth 1 https://github.com/jrmatherly/mcp-context-forgeWrote 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/skills/jrmatherly/mcp-context-forge/mcf-plugin)<a href="https://agentmods.dev/skills/jrmatherly/mcp-context-forge/mcf-plugin"><img src="https://agentmods.dev/badge/skills/jrmatherly/mcp-context-forge/mcf-plugin/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/skills/jrmatherly/mcp-context-forge/mcf-plugin"><img src="https://agentmods.dev/badge/skills/jrmatherly/mcp-context-forge/mcf-plugin.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.00081 | $0.02080 |
| Opus 5 | $0.00041 | $0.01040 |
| Sonnet 5 | $0.00016 | $0.00416 |
| Haiku 4.5 | $0.00008 | $0.00208 |
Grade A, and why
mcf-plugin 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a gateway plugin for: $ARGUMENTS
Plugin Type Decision
Ask the user unless obvious from context:
- Native (in-process) — Python class extending
Plugin. Runs inside the gateway process. Best for transforms, filters, validators, and anything needing low latency. - External (MCP server) — Separate MCP server connected via Streamable HTTP, STDIO, or UDS. Best for integrating third-party services, policies requiring isolation, or non-Python implementations.
Hook Types
Six production hooks — plugins override only the hooks they need:
| Hook | When | Typical Use |
|---|---|---|
prompt_pre_fetch |
Before retrieving a prompt | Validate/transform args, mask PII, block |
prompt_post_fetch |
After rendering a prompt | Filter/sanitize content, add metadata |
tool_pre_invoke |
Before executing a tool | Auth/validation, policy checks, arg mutation, block |
tool_post_invoke |
After tool returns | Redact outputs, transform result, audit |
resource_pre_fetch |
Before fetching a URI | Protocol/domain checks, metadata injection, block |
resource_post_fetch |
After content fetched | Size checks, redaction, content transformation |
Native Plugin
Step 1: Create plugin directory
plugins/<plugin_name>/
<plugin_name>.py # Plugin class
__init__.py # empty
Convention: 42 built-in plugins exist under plugins/. Follow the same flat structure.
Step 2: Write the plugin class
# -*- coding: utf-8 -*-
"""<Plugin description>."""
from mcpgateway.plugins.framework.base import Plugin
from mcpgateway.plugins.framework.models import (
PluginConfig,
PluginContext,
PluginViolation,
ToolPreInvokePayload,
ToolPreInvokeResult,
)
class MyPlugin(Plugin):
"""<Description of what this plugin does>."""
async def tool_pre_invoke(
self, payload: ToolPreInvokePayload, context: PluginContext
) -> ToolPreInvokeResult:
# Access plugin-specific config
threshold = self.config.config.get("threshold", 100)
# Check condition
if some_violation_detected(payload):
return ToolPreInvokeResult(
continue_processing=False,
violation=PluginViolation(
reason="Policy violation",
description="Detailed explanation",
code="MY_PLUGIN_VIOLATION",
details={"matched": True},
),
)
# Pass through (optionally modify payload)
return ToolPreInvokeResult(
continue_processing=True,
modified_payload=payload,
metadata={"checked_by": "my_plugin"},
)
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 · 264 lines · 81 tokens per session scan A 320251d60914
mcf-plugin is a skill published in the GitHub repository jrmatherly/mcp-context-forge (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 2,080 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…