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 instructions/lineai-intelligence/lineai-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/lineai-intelligence/lineai-mcp-serverWrote 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/instructions/lineai-intelligence/lineai-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/lineai-intelligence/lineai-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/lineai-intelligence/lineai-mcp-server/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00714 | $0.00714 |
| Opus 5 | $0.00357 | $0.00357 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
lineai-mcp-server copilot-instructions.md 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lineai MCP Server - AI Assistant Instructions
About This Codebase
This repository contains a Model Context Protocol (MCP) server that integrates with Lineai's knowledge graph APIs. It enables AI programming assistants (like GitHub Copilot and Cursor) to access dependency data from Lineai to analyze code and database impacts.
Key Technologies
- Python 3.13+ with extensive use of async/await
- Model Context Protocol SDK (
mcp[cli]) - Neo4j for graph database operations
- HTTPX for API requests
- Environment variables via dotenv for configuration
Project Structure
- src/lineai_mcp_server/: Core package
__init__.py: Package initialization and entry pointserver.py: MCP server implementationhandlers.py: Tool handlers implementationutils.py: API interaction utilities
Core Coding Patterns
MCP Server Pattern
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
Error Handling
try:
# Operations that might fail
except Exception as e:
sys.stderr.write(f"Error: {str(e)}\n")
return [types.TextContent(type="text", text=f"# Error\n\n{str(e)}")]
Style Guidelines
- Copyright Headers: Include MPL 2.0 headers in all Python files
- Docstrings: Google-style docstrings for modules/classes/functions
- Type Hints: Always use Python type hints
- Asynchronous: Keep I/O operations asynchronous
- Format Outputs: Return markdown-formatted text in tool responses
Tool Implementation Pattern
When implementing new MCP tools:
- Add to
handle_list_tools()with descriptive name (prefix:lineai-) - Add handler in
handle_call_tool() - Implement handler function with 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.
- 6d ago First seen · 100 lines · 714 tokens per session scan A d790001dbc65
lineai-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository lineai-intelligence/lineai-mcp-server (38 stars, last pushed 24d ago), licensed MPL-2.0. It adds 714 tokens to every session, about $0.0036 per session on Opus 5. 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 instructions, from other repositories
python-sdk AGENTS.md
AGENTS.md instructions for modelcontextprotocol/python-sdk, covering development guidelines, note for ai agents, branching model, package management and code quality.
frontmcp AGENTS.md
AGENTS.md instructions for agentfront/frontmcp, a project described as: TypeScript-first framework for the Model Context Protocol (MCP). You write clean, typed code; FrontMCP handles the protocol, transport, DI, session/auth, and execution flow.
brain-in-the-fish CLAUDE.md
Instructions for fabio-rovai/brain-in-the-fish, covering brain in the fish, relationship to open-ontologies, module overview, pipeline and mcp tools.
Web-Algebra CLAUDE.md
Instructions for AtomGraph/Web-Algebra, covering claude.md, project overview, core architecture, key components and commands.
quarry CLAUDE.md
Claude Code instructions for punt-labs/quarry, covering quarry, mandatory reading, architecture, how a query works and how ingestion works.
cdc-health-mcp-server CLAUDE.md
Instructions for cyanheads/cdc-health-mcp-server, covering agent protocol, domain, api surface, socrata api endpoints and cdc wonder api.