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/pulsenpx skills add dancolta/subscope --skill pulsegit 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.00092 | $0.00501 |
| Opus 5 | $0.00046 | $0.00251 |
| Sonnet 5 | $0.00018 | $0.00100 |
| Haiku 4.5 | $0.00009 | $0.00050 |
Grade A, and why
subscope-pulse 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
/subscope-pulse
Weekly reflection layer. Notion is the daily-triage surface; Obsidian is the weekly-review surface where you spot patterns over time.
Preflight
Check for Obsidian vault config:
cat ~/.config/subscope/obsidian.yml 2>/dev/null
Expected shape:
vault_path: /Users/dan/Documents/MyVault
pulse_folder: subscope # optional, defaults to 'subscope'
If obsidian.yml missing: print "Obsidian vault not configured. Run /subscope-onboard to wire it (or drop ~/.config/subscope/obsidian.yml with a vault_path: line manually), then re-run."
Generate digest
cd "$CLAUDE_PLUGIN_ROOT" && PYTHONPATH=engine python3 -c "
from subscope.lib import store, obsidian_sync
with store.connect() as conn:
print(obsidian_sync.build_weekly_digest(conn))
"
That prints the markdown digest content to stdout.
Write to Obsidian
Use the obsidian MCP to write the digest:
- Compute the filename:
YYYY-WNN-pulse.md(current ISO week) - Compute the path:
<vault_path>/<pulse_folder>/<filename>(create the folder if missing) - Call
mcp__obsidian__create-notewith that path and the markdown body from the previous step
If obsidian MCP not available (rare — Dan has it installed by default), fall back to writing the file via the host filesystem (Bash: mkdir -p ... && cat > ...).
After write
Print one line:
Pulse written: <vault_path>/<pulse_folder>/<filename> (N surfaces this week)
Do not print the digest body. Dan reads it in Obsidian.
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 · 57 lines · 92 tokens per session scan A b255ce41bc7b
subscope-pulse is a skill published in the GitHub repository dancolta/subscope (25 stars, last pushed 21d ago), licensed MIT. It adds 92 tokens to every session and 501 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-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.