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/synapsor/synapsor-runner/synapsor-safe-actiongit clone --depth 1 https://github.com/Synapsor/Synapsor-RunnerWhat 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.00117 |
| Opus 5 | $0.00000 | $0.00059 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
synapsor-safe-action 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 2d 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
For files under synapsor/actions/, read and obey
synapsor/SAFE_ACTION_AGENT.md. That file is generated by Runner from the
canonical host-neutral instructions. Drafts must remain disabled. Never modify
active contract state, credentials, trusted scope, Cursor MCP configuration, or
source data, and never introduce raw SQL or model-visible approval/apply tools.
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.
- 2d ago First seen · 13 lines · 0 tokens per session scan A ee1fbd9b18f7
synapsor-safe-action is a cursor rule published in the GitHub repository Synapsor/Synapsor-Runner (2 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 117 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-31.
Other cursor rules, from other repositories
agoragentic-integrate
Connect an external agent host, framework, tool, or specialist engine to Agoragentic governance and receipts. Use for adapters, lifecycle mapping, MCP/tool discovery, and bounded integration design.
cursorrules
This repo has a GraphPilot structural code-graph available via MCP. Use it before grep on structural questions.
qa-agent
QA workflow for reviewing stories, designing tests, and reporting verified defects.
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
clarify-first-prompting
Clarify-first strategy: detect ambiguity, ask targeted questions, expand simple prompts into detailed specifications.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.