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/Othmane-Khadri/YALC-the-GTM-operating-systemWrote 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/othmane-khadri/yalc-the-gtm-operating-system/lemlist)<a href="https://agentmods.dev/mcp/othmane-khadri/yalc-the-gtm-operating-system/lemlist"><img src="https://agentmods.dev/badge/mcp/othmane-khadri/yalc-the-gtm-operating-system/lemlist/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/othmane-khadri/yalc-the-gtm-operating-system/lemlist"><img src="https://agentmods.dev/badge/mcp/othmane-khadri/yalc-the-gtm-operating-system/lemlist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lemlist 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 7d 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
{
"lemlist": {
"command": "npx",
"args": [
"mcp-remote",
"https://app.lemlist.com/mcp",
"--header",
"X-API-Key: ${LEMLIST_API_KEY}"
]
}
}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.
- 7d ago First seen · 11 lines scan A 2125b5f4435c
lemlist is an MCP server published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 21d 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-09-03.
Other mcp servers, from other repositories
knowns
MCP server "knowns" as configured in knowns-dev/knowns. Launched with knowns mcp --stdio.
perseus
Live workspace context engine for AI assistants — resolve before context. Runs locally from the perseus-ctx Python package.
oss-autopilot
Open source contribution manager with PR tracking, issue discovery, and CI diagnosis. Runs locally from the @oss-autopilot/mcp npm package. Needs 1 environment variable to run.
oss-autopilot
MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools. Runs locally from the @oss-autopilot/mcp npm package.
speed-to-lead-agent
MCP server "speed-to-lead-agent" as configured in OmateLabs/speed-to-lead-agent. Runs locally from the speed-to-lead-agent Python package.
prospector
Prospector is a tool to analyse Python code by aggregating the result of other tools. Runs locally from the prospector Python package.