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 agents/pegasi-ai/reins/cursorgit clone --depth 1 https://github.com/pegasi-ai/reinsWhat 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.00346 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
cursor 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
ToolShield + Cursor
Cursor is an AI-powered code editor. ToolShield injects safety guidelines into Cursor's global user rules stored in its internal SQLite database.
How It Works
Cursor stores user rules in a SQLite database (state.vscdb) under the key aicontext.personalContext. ToolShield reads the existing rules, appends safety guidelines, and writes them back. Your existing rules are fully preserved.
Import
toolshield import \
--exp-file postgres-mcp.json \
--agent cursor
You can import multiple tools — each appends to the existing rules:
toolshield import --exp-file terminal-mcp.json --agent cursor
toolshield import --exp-file filesystem-mcp.json --agent cursor
Unload
toolshield unload --agent cursor
This removes all ToolShield-injected guidelines while preserving your existing user rules.
Database Location
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb |
| Linux | ~/.config/Cursor/User/globalStorage/state.vscdb |
| Windows | %APPDATA%\Cursor\User\globalStorage\state.vscdb |
Notes
- ToolShield writes to the global user rules (not project-level
.cursor/rules/), so guidelines apply across all projects. - Cursor must be restarted (or the rules reloaded) for changes to take effect.
- If Cursor is installed in a non-default location, use
--source_locationto point to a plain text file instead.
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 · 45 lines · 0 tokens per session scan A dffa527fde9f
cursor is an agent published in the GitHub repository pegasi-ai/reins (408 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 346 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 agents, from other repositories
implementer
You are the implementer agent in the Polis automated pipeline.
architect
You are the architecture agent in the Polis automated pipeline.
fixer
You are the fixer agent in the Polis automated pipeline.
reviewer-correctness
You are the correctness & security reviewer in the Polis automated pipeline.
spec-designer
You are the spec-design agent in the Polis automated pipeline.
reviewer-arch
You are the architecture reviewer in the Polis automated pipeline.