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 skills add INo-xious/stockbit-mcp --skill stockbit-authgit clone --depth 1 https://github.com/INo-xious/stockbit-mcpWrote 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/ino-xious/stockbit-mcp/stockbit-auth)<a href="https://agentmods.dev/skills/ino-xious/stockbit-mcp/stockbit-auth"><img src="https://agentmods.dev/badge/skills/ino-xious/stockbit-mcp/stockbit-auth/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/ino-xious/stockbit-mcp/stockbit-auth"><img src="https://agentmods.dev/badge/skills/ino-xious/stockbit-mcp/stockbit-auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 27 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00063 | $0.00656 |
| Opus 5.5 | $0.00025 | $0.00262 |
| Sonnet 5.5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
stockbit-auth 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stockbit login
Launch the browser login and confirm the refresh token was captured.
Step 1 — launch it detached
stockbit-auth login
(or node dist/bin/stockbit-auth.js login from the repo root; add --fresh-profile if a saved browser profile is stuck.)
If you are an agent running this through a tool harness, do not run it as a foreground or backgrounded shell call. Harnesses that reap the process tree when a turn ends will kill node mid-login, and node's cleanup closes the browser with it — the login never completes and the failure looks like a browser problem. Launch it as a detached process instead, so it outlives the turn. On Windows:
Start-Process -FilePath "node" -ArgumentList "dist\bin\stockbit-auth.js", "login" `
-WorkingDirectory <repo-root> -WindowStyle Hidden `
-RedirectStandardOutput "$env:TEMP\stockbit-login.out.log" `
-RedirectStandardError "$env:TEMP\stockbit-login.err.log"
On macOS/Linux, detach with nohup ... & or an equivalent that survives the caller.
Step 2 — hand the browser to the user
A browser window opens on the Stockbit login page. The user logs in there themselves. The session is captured automatically the moment login completes, and the window may close itself. The flow allows up to 15 minutes.
Never ask for the user's Stockbit password and never type credentials on their behalf — the browser session is theirs. Then wait for them to say they are done; do not poll in a loop.
Step 3 — verify
Read the redirected logs (success prints Session captured and a passing test refresh), then confirm the stored token independently:
stockbit-auth status
Expect Validity: OK. Note that status can print correctly and then crash on a libuv assertion on Windows — judge by the text, not the exit code. Remind the user that ordinary use keeps the window sliding, and only a long idle gap forces another login.
If the browser flow fails
Offer the fallbacks in this order:
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.
- 1mo ago First seen · 54 lines · 63 tokens per session scan A 06515ac47013
stockbit-auth is a skill published in the GitHub repository INo-xious/stockbit-mcp (55 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 656 once invoked, about $0.0003 per session on Opus 5.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
tradingview-mcp
AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, licensed news sentiment (Marketaux), and multi-market screener. Supports stocks, crypto, ETFs, indices, Turkish (BIST), and Egyptian (EGX) markets.
escalation
Escalate a disputed refund to the billing lead.
refunds
Process customer refunds.
error-handling
Read the error codes these tools raise and decide whether to retry, fix the call, or stop.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.