LiveStore is a state-management framework that stores application data in SQLite, a database embedded in the application, and synchronizes that data through a built-in engine. It is intended for applications that keep data locally while supporting reactive updates and synchronization.
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/livestorejs/livestore/mcpgit clone --depth 1 https://github.com/livestorejs/livestoreWrote 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/rules/livestorejs/livestore/mcp)<a href="https://agentmods.dev/rules/livestorejs/livestore/mcp"><img src="https://agentmods.dev/badge/rules/livestorejs/livestore/mcp.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.00086 | $0.00086 |
| Opus 5 | $0.00043 | $0.00043 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
mcp 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 yesterday.
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
GitHub MCP
Use the livestorejs/livestore repo (unless asked differently) for GitHub repo management (e.g. issues, PRs...)
Don't create new issue labels unless asked.
Before creating new issues, search existing issues for potential duplicates/overlaps and clarify if needed.
When creating an issue, print a clickable link.
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.
- yesterday First seen · 11 lines · 86 tokens per session scan A 8d240eacea64
mcp is a cursor rule published in the GitHub repository livestorejs/livestore (3,695 stars, last pushed yesterday), licensed Apache-2.0. It adds 86 tokens to every session, about $0.0004 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-09-04.
Other cursor rules, from other repositories
project-context
Copilot – quick read, commands, and where to find more.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
git_rules
When asked to interact with git, github or project management tooling (jira, linear, asana etc).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.