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/signalscope/cursor-plugin/signalscope-apigit clone --depth 1 https://github.com/signalscope/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/signalscope/cursor-plugin/signalscope-api)<a href="https://agentmods.dev/rules/signalscope/cursor-plugin/signalscope-api"><img src="https://agentmods.dev/badge/rules/signalscope/cursor-plugin/signalscope-api.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.00015 | $0.01006 |
| Opus 5 | $0.00008 | $0.00503 |
| Sonnet 5 | $0.00003 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
signalscope-api 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SignalScope API Conventions
Authentication
Two methods — the MCP server uses whichever is configured:
SIGNALSCOPE_API_KEY— subscription-based. Flat rate, full access, daily quota. Generate at signalscopes.com/profile.SIGNALSCOPE_WALLET_PRIVATE_KEY— x402 pay-per-call in USDC on Base. No account needed. Costs: trending/network $0.01, ticker/history/performance/related $0.005, AI report $0.05.
Free (no auth): search_tickers, get_methodology.
API key only (not x402): list_scans, get_scan, get_signals, portfolio, watchlist, prices, stats.
Symbol format
Always pass ticker symbols in UPPERCASE. The MCP tools normalise automatically, but be consistent in output and reasoning (AAPL, not aapl or Aapl).
Signal stages
| Stage | Meaning | Sources |
|---|---|---|
Emerging |
Low-conviction — only 1 source detected this ticker | 1 |
Building |
Building conviction — 2 sources | 2 |
Consensus |
High-conviction breakout signal | 3+ |
Filtered |
Pump-and-dump flagged — excluded from default results | — |
Prefer Consensus for trade recommendations. Building is valid for watchlist adds. Emerging warrants further research before acting.
AI score vs Opportunity score
- AI score (0–100): Evidence strength — how strongly the underlying signals support a breakout thesis
- Opportunity score: Early-mover rank within the scan — how early this ticker was detected relative to others
Both are available in get_trending sortBy options (aiScore, opportunityScore).
AI score interpretation
| Score | Signal strength |
|---|---|
| 70–100 | Strong — high confidence breakout candidate |
| 50–69 | Moderate — worth monitoring |
| 0–49 | Weak — low conviction, caution advised |
P&D flags
If pndFlagged: true, the ticker triggered 3+ of SignalScope's 11 pump-and-dump detection rules. Treat these with significant caution. The pndFlags array lists which specific flags triggered.
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.
- 4d ago First seen · 95 lines · 15 tokens per session scan A e215f1f51ce2
signalscope-api is a cursor rule published in the GitHub repository signalscope/cursor-plugin (0 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 1,006 once invoked, about $0.0001 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 cursor rules, from other repositories
lighter-safety
Safety contract for the Lighter MCP server. Apply whenever a lighter tool is invoked.
elizaos_v2_onchain_plugins
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │ Wallet Provider│ │ Connection Mgmt │ │ Transaction Svc │ │ - Private Keys │───▶│ - RPC Endpoints │───▶│ - Tx Construction│ │ - Public Keys │ │ - Network Config │ │ - Fee Estimation│ │ - Signatures │ │ - Health Check │ │ - Broadcasting │ └─────────────────┘…
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.