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 mcp/openly-useful/linear-project-skills/linear_projectgit clone --depth 1 https://github.com/Openly-Useful/linear-project-skillsWrote 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/openly-useful/linear-project-skills/linear_project)<a href="https://agentmods.dev/mcp/openly-useful/linear-project-skills/linear_project"><img src="https://agentmods.dev/badge/mcp/openly-useful/linear-project-skills/linear_project.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
linear_project 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 4d 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
{
"linear_project": {
"args": [
"--yes",
"--package",
"@openly-useful/[email protected]",
"--",
"node",
"-e",
"const{delimiter,resolve}=require(\"node:path\"),{pathToFileURL}=require(\"node:url\");const bin=process.env.PATH?.split(delimiter)[0];if(!bin)throw new Error(\"npm exec PATH is missing\");const entry=resolve(bin,\"..\",\"@openly-useful\",\"linear-project-mcp-server\",\"dist\",\"index.js\");process.argv[1]=entry;import(pathToFileURL(entry).href);"
],
"command": "npx"
}
}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.
- 4d ago First seen · 14 lines scan A 28439f502696
linear_project is an MCP server published in the GitHub repository Openly-Useful/linear-project-skills (0 stars, last pushed 12d 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
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.
mem0
MCP server "mem0" as configured in mem0ai/mem0. Runs ${CLAUDE_PLUGIN_ROOT}/core/mcp_server.py with python3. Needs 1 environment variable to run.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const…