agentmods.dev

crypto-quant-signal-mcp: Command for Claude Code

.claude/commands/geo-decide.md

geo-decide is a command for Claude Code from AlgoVaultLabs/crypto-quant-signal-mcp. It costs 13 tokens per session (348 once invoked), scanned A, original, MIT.

A command that reads a weekly GEO decision brief and starts a review process for choosing search-visibility work. GEO here means improving how content is found and represented by generative search engines.

In plain words
What is it for?
Use it to review the top candidate, write an action specification, request approval, dispatch the work, and record its progress and results.
Why use it?
It turns the latest scored recommendation into a concrete, reviewed action instead of leaving the decision in a database or dashboard.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is AlgoVaultLabs/crypto-quant-signal-mcp's own configuration. It tells Claude Code how to work on crypto-quant-signal-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything crypto-quant-signal-mcp configures →

not rated 7repo today A scan 13 tokens original MIT
View source ↗ AlgoVaultLabs/crypto-quant-signal-mcp algovault.com
Reuse

Borrowing it

Nothing to install: this file belongs to AlgoVaultLabs/crypto-quant-signal-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AlgoVaultLabs/crypto-quant-signal-mcp/main/.claude/commands/geo-decide.md
Clone the repo
git clone --depth 1 https://github.com/AlgoVaultLabs/crypto-quant-signal-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for geo-decide

README.md
[![agentmods](https://agentmods.dev/badge/commands/algovaultlabs/crypto-quant-signal-mcp/geo-decide/github.svg)](https://agentmods.dev/commands/algovaultlabs/crypto-quant-signal-mcp/geo-decide)
Your own site
<a href="https://agentmods.dev/commands/algovaultlabs/crypto-quant-signal-mcp/geo-decide"><img src="https://agentmods.dev/badge/commands/algovaultlabs/crypto-quant-signal-mcp/geo-decide/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.

agentmods 80×15 button for geo-decide

Your own site · 80×15
<a href="https://agentmods.dev/commands/algovaultlabs/crypto-quant-signal-mcp/geo-decide"><img src="https://agentmods.dev/badge/commands/algovaultlabs/crypto-quant-signal-mcp/geo-decide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 348 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00013 $0.00348
Opus 5 $0.00006 $0.00174
Sonnet 5 $0.00003 $0.00070
Haiku 4.5 $0.00001 $0.00035

Measured 11d ago against content hash 6a02896f2d44, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

geo-decide 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 11d 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.

.claude/commands/geo-decide.md · 25 lines

What it actually says

Run the GEO Decide review now (manual trigger; the canonical schedule is the Mon 08:00 UTC cron).

  1. Read the latest scored decision from Postgres (the cross-host boundary):

    ssh -i ~/.ssh/algovault_deploy [email protected] \
  "docker exec crypto-quant-signal-mcp-postgres-1 psql -U algovault -d signal_performance \
   -c \"SELECT created_at, priority_tier, status, chosen_move FROM geo_decisions ORDER BY created_at DESC LIMIT 1\" \
   -c \"SELECT rendered_brief FROM geo_decisions ORDER BY created_at DESC LIMIT 1\""

    (or open the dashboard: https://api.algovault.com/admin/geo-dashboard?key= → "🎯 This week's decision").

  2. Materialize the brief into the vault as Prompt/geo-decision-<date>.md.

  3. Deep-research the top candidate per the priority gate: why the leader wins it, the concrete move, expected lift, target engine, which sub-goal (A/B/C). Author the Tier-1/2 action spec.

  4. Hand to Mr.1 to approve → dispatch to Code (/goal-gated) → completion to status.md only (NO Telegram). Flip geo_decisions.status proposed → approved → executed → measured.

Full runbook: docs/GEO-DECIDE-RITUAL.md. Tuning SoT: landing/Prompt/geo-objective.yaml.

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. 11d ago First seen · 25 lines · 13 tokens per session scan A 6a02896f2d44

Subscribe to this mod's changes

geo-decide is a command published in the GitHub repository AlgoVaultLabs/crypto-quant-signal-mcp (7 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 348 once invoked, about $0.0001 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-31.

Marketing and SEOPlanningai-agentsbasecryptodefifunding-ratemcp
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens