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/dancolta/subscope/setupnpx skills add dancolta/subscope --skill setupgit clone --depth 1 https://github.com/dancolta/subscopeWhat 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.00105 | $0.02139 |
| Opus 5 | $0.00053 | $0.01069 |
| Sonnet 5 | $0.00021 | $0.00428 |
| Haiku 4.5 | $0.00011 | $0.00214 |
Grade B, and why
subscope-setup scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
The helper writes to `~/.config/subscope/notion.yml` with `chmod 600` from the moment the file appears (atomic, no umask race). How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/subscope-setup
Reconfiguration tool for an already-onboarded subscope install. For first-run, route the user to /subscope-onboard instead. The 6 steps below are now individually addressable: ask the user which one they want to change before walking the whole flow.
Goal
Let an existing user change one piece of their config without re-doing the whole onboarding.
Procedure
First, check whether the user has already onboarded:
[ -f ~/.config/subscope/subreddits.yml ] && echo "ONBOARDED" || echo "NOT_ONBOARDED"
If NOT_ONBOARDED: redirect to /subscope-onboard and stop. Do not run the steps below for a new install.
If ONBOARDED: ask which piece they want to change:
What do you want to reconfigure?
- LLM provider (add or swap)
- Targeting (re-pick preset, or re-run /subscope-onboard for full re-do)
- Notion database
- Slack webhook
- Obsidian vault
Pick a number, or type "all" to walk every step.
Then jump to that step only. Each step is independent.
Step 1 — LLM provider (optional)
Tell the user:
subscope has three classification tiers:
- Default: regex-only gate, zero cost, no API key needed.
- Interactive:
/subscope-judge <surface-id>uses your Claude Code subscription, free.- Bulk LLM: any OpenAI-compatible provider (Anthropic, OpenAI, Groq, OpenRouter, Together, local Ollama). ~$0.50/day at 5K posts.
Want to enable the bulk-LLM tier? (yes / skip)
If yes, the user sets one env var (LLM_API_KEY, or legacy ANTHROPIC_API_KEY / OPENAI_API_KEY). The base URL is auto-detected from the key prefix (sk-ant- → Anthropic /openai/v1, sk-or- → OpenRouter, gsk_ → Groq, else OpenAI). For local Ollama or a custom endpoint, also set LLM_BASE_URL.
To lock the preference, write a minimal ~/.config/subscope/llm.json:
{"provider": "openai_compatible"}
Test the resolved config (this will also fail loudly if LLM_BASE_URL targets a private IP — the SSRF guard is intentional):
cd "$CLAUDE_PLUGIN_ROOT" && PYTHONPATH=engine python3 -c "
from subscope.lib import classify
import json
print(json.dumps(classify.status(), indent=2))
"
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 · 206 lines · 105 tokens per session scan B 56a26ee86b78
subscope-setup is a skill published in the GitHub repository dancolta/subscope (25 stars, last pushed 20d ago), licensed MIT. It adds 105 tokens to every session and 2,139 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
broker-integration
Integrate a new Indian broker into OpenAlgo, or modify an existing broker plugin. Use when wiring up a broker's auth/login, orders, quotes, depth, history, funds, margin, symbol master, or WebSocket streaming; when a broker does not appear in the login dropdown or fails to load; or when debugging broker-specific…
chart-indicator
Build a custom indicator for the OpenAlgo /trading charting terminal (openalgo-charts). Use when asked to create, port, or debug a chart indicator, overlay, oscillator, band, or on-chart signal, including porting a study written for another charting platform. Writes a plain-JS descriptor into strategies/indicators/…
rekal-init
Bootstrap rekal memory for a project. Scans the codebase for architecture, conventions, dependencies, workflows, and config, then stores durable knowledge as properly typed, tagged, deduplicated memories. Use when starting rekal on a new project, or when user says "init rekal", "bootstrap memory", "populate rekal"…
fd-audit
Audit a change for resource leaks in OpenAlgo — file descriptors AND unbounded memory growth. Run after building a feature or fixing anything that touches databases, WebSockets or streaming, threads or executors, subprocesses, files, sockets, caches, or module-level registries. Also use when the user reports "too many…
flow-builder
Build, edit or debug an OpenAlgo Flow workflow - the no-code node graph at /flow. Use when asked to create a workflow, wire a webhook or TradingView alert to an order, add a node, port a strategy into Flow, or work out why a workflow imported but did nothing. Produces a workflow JSON that is validated against the real…
security-audit
Run OpenAlgo's periodic security audit across backend, frontend, database, cache, routes and dependencies, producing a dated xlsx report. Use for the monthly or twice-monthly review, before a release, after a dependency bump, or when the user asks for a security check, vulnerability scan, or audit report.