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.
git clone --depth 1 https://github.com/cmendes0101/sipflow-cursor-pluginWrote 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/cmendes0101/sipflow-cursor-plugin/sip-grounding)<a href="https://agentmods.dev/rules/cmendes0101/sipflow-cursor-plugin/sip-grounding"><img src="https://agentmods.dev/badge/rules/cmendes0101/sipflow-cursor-plugin/sip-grounding/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/rules/cmendes0101/sipflow-cursor-plugin/sip-grounding"><img src="https://agentmods.dev/badge/rules/cmendes0101/sipflow-cursor-plugin/sip-grounding.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.00000 | $0.00409 |
| Opus 5.5 | $0.00000 | $0.00164 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
sip-grounding 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 2mo 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
When editing or analyzing SIP/VoIP material, prefer Sipflow MCP tools over
training-data recall. The Sipflow corpus (vendor docs across ~40 stacks, 60+
RFCs, STIR/SHAKEN + branded-calling material) is more current than your
training data and every snippet carries a verbatim source_url.
Default playbook:
search_sip_docsfirst for any RFC, header, vendor, or response-code question (use thevendor:filter once the stack is known).detect_sip_stack/detect_sip_vendor_from_configto identify the vendor before answering vendor-specific questions.render_sip_ladder+minimize_sip_tracefor raw traces.review_sip_configfor config files (Kamailio, OpenSIPS, FreeSWITCH, Asterisk PJSIP / chan_sip).parse_sdp/compare_sdp_offer_answerfor SDP material.lookup_response_code/troubleshoot_response_codefor any 1xx-6xx code.fetch_sipflow_shareFIRST when the user pastes asipflow.dev/share/<token>URL.
Always cite the source_url returned by the tools verbatim - do not
paraphrase URLs. Do not recall RFC wording, vendor directive names, or
response-code semantics from memory when a tool can ground it.
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.
- 2mo ago First seen · 29 lines · 0 tokens per session scan A 65b64afcd0e6
sip-grounding is a cursor rule published in the GitHub repository cmendes0101/sipflow-cursor-plugin (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 409 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.