setup

A command that sets up MEICAgent’s broker credentials and checks whether it can connect. Credentials are saved in the operating system’s secure keyring, such as macOS Keychain or Windows Credential Manager.

In plain words
What is it for?
Use it to check credential status, enter a client secret or refresh token, optionally set an account number, and verify the broker connection.
Why use it?
It identifies missing login details and provides a controlled way to add or update them without displaying secret values on screen.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/joncovington/meicagent/setup
Clone the repo
git clone --depth 1 https://github.com/joncovington/MEICAgent

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 588 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00588
Opus 5 $0.00000 $0.00294
Sonnet 5 $0.00000 $0.00118
Haiku 4.5 $0.00000 $0.00059

Measured yesterday against content hash 24030fa999f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 yesterday.

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.

.claude/commands/setup.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up MEICAgent credentials and verify the broker connection.

Step 1 — Check current credential status

python src/tt.py secrets_status

Report which secrets are set and which are missing. The two required secrets are client_secret and refresh_token. account_number is optional (the SDK discovers accounts automatically if omitted).

Step 2 — Set missing credentials

If any required secrets are missing, instruct the user to run this command in their own terminal (not here — getpass requires interactive input):

python src/tt.py secrets_set

This prompts for each credential with hidden input (no echo) and stores them in the OS keyring (Windows Credential Manager / macOS Keychain / Linux Secret Service). Existing values are preserved if the user presses Enter without typing.

To update a single key only:

python src/tt.py secrets_set --keys refresh_token

Tell the user: credentials are stored under service name meicagent in the OS keyring. secrets_set/get_secret also fall back to reading the older tastytrade-mcp service name (read-only) so anyone with credentials already stored under it don't need to re-enter them — new writes always go to meicagent.

Step 3 — Verify connection

After the user confirms credentials are set, test the broker connection:

python src/tt.py get_connection_status

A successful response includes "ok": true and account details. If it fails:

  • 401 Unauthorized: refresh token is expired — the user needs to re-authenticate via tastytrade and obtain a new refresh token
  • NoKeyringError: no keyring backend — on Linux, install python3-keyring or gnome-keyring
  • CredentialError: keyring read failure — check OS keyring permissions

Step 4 — Verify account access

python src/tt.py get_account_info

Confirm buying power and NLV are visible. If the wrong account appears, set the explicit account number:

python src/tt.py secrets_set --keys account_number

Read the full file on GitHub · 75 lines

Changes

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.

  1. yesterday First seen · 75 lines · 0 tokens per session scan A 24030fa999f1

Subscribe to this mod's changes

setup is a command published in the GitHub repository joncovington/MEICAgent (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 588 tokens. 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.