Borrowing it
Nothing to install: this file belongs to proAutomator/livespace-crm-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/proAutomator/livespace-crm-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/proAutomator/livespace-crm-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/instructions/proautomator/livespace-crm-mcp/agents-md)<a href="https://agentmods.dev/instructions/proautomator/livespace-crm-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/proautomator/livespace-crm-mcp/agents-md/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/instructions/proautomator/livespace-crm-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/proautomator/livespace-crm-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01100 | $0.01100 |
| Opus 5 | $0.00550 | $0.00550 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
livespace-crm-mcp AGENTS.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 8d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
livespace-crm-mcp - Agent Instructions
Unofficial MCP server for Livespace CRM. ~10 intent-shaped tools instead of a
1:1 mirror of the ~80-method RPC API. Target protocol: MCP 2026-07-28
(stateless Streamable HTTP). Stack: TypeScript (strict) + Hono, Bun/Node with
a planned Cloudflare Workers dual runtime, @modelcontextprotocol/server v2
pinned to an exact version.
Hard rules
- Read
docs/security.mdbefore touching auth, the Livespace client, transport, or error handling. Its MUSTs are binding; code violating them does not ship. - No secrets, no real CRM data - anywhere. Not in code, tests, fixtures,
docs, commit messages, or
.ai/files. Fixtures are synthetic and every fake credential value MUST contain the word "synthetic" (e.g.synthetic-key-123) -.gitleaks.tomlallowlists that marker and nothing else, so CI stays green without weakening the scanner. This repo's full history is expected to become public. - Never log tokens or full CRM payloads. Errors surfaced to the model must never contain upstream response bodies or stack traces.
- TDD. Write the failing test first. Every tool ships with contract tests;
security regressions from
docs/security.md§10 stay green. - English for code, comments, commits, and docs.
- Do not change the default bind (
127.0.0.1) or weaken fail-closed startup checks without an explicit maintainer decision. - Do not commit or push unless Kuba asks.
Livespace API - facts that will bite you
- Success is
status: true && result: 200in the response envelope; HTTP is 200 even on errors. Always check the envelope. - The official Postman docs contain errors (e.g. "delete deal" shown as
Contact/deleteDeal; PDF v1.13 saysDeal/deleteDeal). Trust the API PDF over the Postman portal and confirm every method with a live smoke test on a sandbox account before release. Deal/getAllrequires at least one condition. List endpoints default to returning ALL records - send an explicitlimitwhere the endpoint supports it.Todo/getTodoObjectsuses fixed 50-row pages; dictionary endpoints that ignorelimitneed bounded local caps.- There is no "set stage" call: stage changes = marking process steps via
editDeal stages{step_id: 0|1}mapped fromDeal/process_getList. - Every logical call costs 2 HTTP requests (auth token + call): batch aggressively, cache dictionaries in memory with TTL.
- Select-type custom fields (datasets) take answer IDs, not display 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.
- 8d ago First seen · 84 lines · 1,100 tokens per session scan A d71657e7a57a
livespace-crm-mcp AGENTS.md is an instructions file published in the GitHub repository proAutomator/livespace-crm-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,100 tokens to every session, about $0.0055 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.