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 skills/cmendes0101/sipflow-cursor-plugin/sip-debuggernpx skills add cmendes0101/sipflow-cursor-plugin --skill sip-debuggergit 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/skills/cmendes0101/sipflow-cursor-plugin/sip-debugger)<a href="https://agentmods.dev/skills/cmendes0101/sipflow-cursor-plugin/sip-debugger"><img src="https://agentmods.dev/badge/skills/cmendes0101/sipflow-cursor-plugin/sip-debugger.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 | $0.00094 | $0.01188 |
| Opus 5 | $0.00047 | $0.00594 |
| Sonnet 5 | $0.00019 | $0.00238 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
sip-debugger 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sipflow SIP/VoIP Debugger
When to use
Reach for this skill whenever the user's request touches:
- SIP signaling - methods, headers, response codes, dialog state, transactions
- RTP / SDP - codecs, DTMF, ICE/STUN/TURN, WebRTC
- STIR/SHAKEN, ATIS-1000074/094/084, CTIA Branded Calling
- Vendor configs - Kamailio, OpenSIPS, FreeSWITCH, Asterisk (PJSIP and chan_sip), SIP.js, JsSIP, FreePBX, 3CX, OpenSER, ~40 stacks total
- Carrier or interop debugging - DNS NAPTR/SRV, TLS, mTLS, fingerprints
- Pasted traces, PCAPs, dialplan snippets, sipflow.dev/share/ URLs
If you are NOT sure whether the question is "SIP enough" - it is. Use the
tools. The corpus is more current than your training data and every snippet
carries a verbatim source_url you can cite.
Core rule: do not recall, ground
NEVER answer from training memory when a Sipflow tool can ground it. This applies even when the user supplies an exact RFC number, vendor name, or section reference - the tool's answer is canonical and cite-able.
Tool catalog
All tools are read-only and side-effect free. The only outbound IO is
dns_diagnose_sip_target (DNS + TLS handshakes) and
validate_stir_shaken_identity (cert fetch). In Cursor's Ask mode, switch to
Agent mode to invoke them.
Discovery / grounding (start here)
search_sip_docs- hybrid BM25 + vector search across the curated VoIP corpus (vendor docs + 60+ RFCs + STIR/SHAKEN + branded calling). Supports avendor:filter.lookup_response_code- sub-millisecond lookup for any 1xx-6xx code.lookup_sip_header- canonical or compact form (Via/v, PAI, Identity, ...).
Detection
detect_sip_stack- vendor from a trace OR a config blob.detect_sip_vendor_from_config- heuristic vendor ID from config text.
Traces
minimize_sip_trace- prune noise headers from a raw trace.render_sip_ladder- SIP trace -> Mermaid sequenceDiagram.sip_ladder_example- canonical example ladders for common flows.lint_sip_request,parse_sip_message,diff_sip_messages.
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 · 105 lines · 94 tokens per session scan A fe7c47a54eb0
sip-debugger is a skill published in the GitHub repository cmendes0101/sipflow-cursor-plugin (0 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 1,188 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…