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.
git clone --depth 1 https://github.com/joaocarlos/writing-context-rtfmWrote 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/mcp/joaocarlos/writing-context-rtfm/writing-context-rtfm)<a href="https://agentmods.dev/mcp/joaocarlos/writing-context-rtfm/writing-context-rtfm"><img src="https://agentmods.dev/badge/mcp/joaocarlos/writing-context-rtfm/writing-context-rtfm/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/mcp/joaocarlos/writing-context-rtfm/writing-context-rtfm"><img src="https://agentmods.dev/badge/mcp/joaocarlos/writing-context-rtfm/writing-context-rtfm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
writing-context-rtfm 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.
What it actually says
{
"writing-context-rtfm": {
"command": "uv",
"args": [
"run",
"writing-context-rtfm",
"serve"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 10 lines scan A 6d1a97cea715
writing-context-rtfm is an MCP server published in the GitHub repository joaocarlos/writing-context-rtfm (2 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
vault-mind
MCP server "vault-mind" as configured in Statutecontempt951/obsidian-llm-wiki. Runs mcp-server/dist/index.js with node.
technocore-chat
MCP server for technocore-chat: shared rooms, durable notes and rendezvous for agents, over plain HTTP. Runs locally from the technocore-mcp Python package. Needs 2 environment variables to run.
mcp
Memory the human governs, on their own machine, plus what other coding agents here wrote. Runs locally from the @mnemosyne_os/mcp npm package. Needs 3 environment variables to run.
palinode
MCP server "palinode" as configured in phasespace-labs/palinode. Launched with palinode-mcp.
memex
Temporal engineering context for agents via MCP. Runs locally from the stifler-memex-mcp npm package. Needs 4 environment variables to run.
kiagent
Your mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. Remote server at {subdomain}.localkiagent.com.