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/lazylagom/context-compose-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/mcp/lazylagom/context-compose-mcp/context-compose)<a href="https://agentmods.dev/mcp/lazylagom/context-compose-mcp/context-compose"><img src="https://agentmods.dev/badge/mcp/lazylagom/context-compose-mcp/context-compose/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/lazylagom/context-compose-mcp/context-compose"><img src="https://agentmods.dev/badge/mcp/lazylagom/context-compose-mcp/context-compose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-compose 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 1mo 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
{ "context-compose": { "command": "npx", "args": [ "-y", "@noanswer/context-compose" ] } }
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.
- 1mo ago First seen · 9 lines scan A 12a745226acf
context-compose is an MCP server published in the GitHub repository lazylagom/context-compose-mcp (1 stars, last pushed 1y ago), 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
meta-prompt-mcp
An MCP server that acts as a Prompting Oracle — advice from official Prompting Guides. Runs locally from the meta-prompt-mcp Python package.
token-compressor
MCP server that compresses prompts 40-60% using local LLM + embedding validation. Runs locally from the token-compressor-mcp Python package.
spec-score-mcp
Score your specs before feeding them to an LLM. MCP server with radar chart visualization. Runs locally from the spec-score-mcp npm package.
thinking-prompts
MCP server "thinking-prompts" as configured in zdrjson/thinking-prompts-skill. Runs locally from the thinking-prompts npm package.
mercury-spec-ops
Modular MCP server for dynamic prompt generation and software development analysis tools. Runs locally from the @n0zer0d4y/mercury-spec-ops npm package.
prompt-library-mcp-server
Community-driven library of tested prompts and MCP tool configurations — npm for AI agent configs. Runs locally from the prompt-library-mcp-server Python package.