Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mphinance/alpha-skillsnpx agentmods add skills/mphinance/alpha-skills/broker-upstream-checkWrote 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/mphinance/alpha-skills/broker-upstream-check)<a href="https://agentmods.dev/skills/mphinance/alpha-skills/broker-upstream-check"><img src="https://agentmods.dev/badge/skills/mphinance/alpha-skills/broker-upstream-check/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/skills/mphinance/alpha-skills/broker-upstream-check"><img src="https://agentmods.dev/badge/skills/mphinance/alpha-skills/broker-upstream-check.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.00103 | $0.00977 |
| Opus 5.5 | $0.00041 | $0.00391 |
| Sonnet 5.5 | $0.00021 | $0.00195 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
broker-upstream-check scanned grade A 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
browser (Claude in Chrome passes Cloudflare where curl and headless Chromium do not), note it How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broker upstream check
scripts/check-freshness.mjs asks how old our date is. This asks whether they changed.
Run it
node scripts/check-upstream.mjs # diff vs scripts/upstream-snapshot.json
node scripts/check-upstream.mjs robinhood etrade # only these slugs
node scripts/check-upstream.mjs --update # diff, then accept the new state as the snapshot
node scripts/check-upstream.mjs --strict # exit 1 on any change (CI)
Takes ~90s for all entries (8 parallel probes, 12s timeout, one retry on transient failure, browser UA).
The last line, coverage:, says how many llms/openapi surfaces are readable, blocked, or absent.
A 403 is ambiguous: bot wall, or "no such file" (S3/CloudFront and API gateways 403 every missing path; robinhood.com, upstox.com and api.connecttrade.com do). So each 403 origin is asked about a path that cannot exist; if that canary also gets 403, the surface is absent, not blocked. "Blocked" means a real wall (e.g. thinkmarkets.com serves a Cloudflare challenge).
Walled sites cannot be watched by the script. Read the page by hand in a real desktop
browser (Claude in Chrome passes Cloudflare where curl and headless Chromium do not), note it
in the entry's caveats, and only then bump last_verified. Wayback availability is a weak
fallback: it lags and rate-limits.
Reading the output
| Tag | Meaning | Action |
|---|---|---|
CHANGED |
llms.txt / openapi.json / cited page / repo release or push moved | Open it, diff against the entry, update the entry if a claim is now wrong, then bump last_verified |
NEW |
A surface appeared that wasn't there (a broker just shipped llms.txt or an OpenAPI spec) | Read it; a new spec often means a new API or MCP route |
GONE |
A surface vanished or a repo got archived | Entry likely needs a status downgrade |
DEAD |
MCP endpoint 404/unreachable, or a cited page 404s | Verify by hand; fix the link or the status |
BLIND |
A surface that used to read fine is now 403/timeout/5xx. Not a change, not a removal | Re-run later; ignore unless it persists |
BASELINE |
First run only, lists what exists | Nothing |
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.
- 9d ago First seen · 56 lines · 103 tokens per session scan A 93fded90b00b
broker-upstream-check is a skill published in the GitHub repository mphinance/alpha-skills (28 stars, last pushed 10d ago), licensed MIT. It adds 103 tokens to every session and 977 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-10.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…