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 rules/lineai-intelligence/lineai-mcp-server/mcp-server-patterngit clone --depth 1 https://github.com/lineai-intelligence/lineai-mcp-serverWhat 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 | $0.00000 | $0.00167 |
| Opus 5 | $0.00000 | $0.00084 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
mcp-server-pattern 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 3d 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
Use the following pattern for MCP server implementation
server = Server("lineai-mcp-server")
@server.list_tools()
async def handle_list_tools() -> list[types.Tool]:
# Define and return tools
@server.call_tool()
async def handle_call_tool(name: str, arguments: dict | None) -> list[types.TextContent]:
# Handle tool execution
- New tools should be added to
handlers/__init__.pyhandle_list_tools()with descriptive names (prefix:lineai-) - Tool handlers should be routed in
handle_call_tool() - Create handler functions with proper error handling
- Return results as markdown-formatted text
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.
- 3d ago First seen · 25 lines · 0 tokens per session scan A cfe89141acb2
mcp-server-pattern is a cursor rule published in the GitHub repository lineai-intelligence/lineai-mcp-server (38 stars, last pushed 21d ago), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 167 tokens. 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-30.
Other cursor rules, from other repositories
codegraph
CodeGraph MCP usage guide — when to use which tool.
faq_usage
Quick reference for when to use DESIGNFAQ.md vs DXFAQ.md.
typescript-coding-rule
It allows a subset of JSDoc tags. Most tags must occupy their own line, with the tag at the beginning of the line.
qa-agent
QA workflow for reviewing stories, designing tests, and reporting verified defects.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.