configure

A setup command for running semantic-search-http as a background service and registering it as an MCP connection. Semantic search finds relevant text by meaning rather than only matching exact words.

In plain words
What is it for?
Use it to install and configure the service on macOS or Linux, create its background service, and connect it to Claude Code.
Why use it?
It avoids starting a separate search service for every coding session and checks for existing services or registrations before changing anything.

Command

Part of the semantic-search plugin — 4 commands, 1 agent shipped together

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/bborbe/semantic-search/configure
Clone the repo
git clone --depth 1 https://github.com/bborbe/semantic-search

Or install semantic-search, the plugin that ships this one along with the rest of its 4 commands, 1 agent.

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,143 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00024 $0.02143
Opus 5 $0.00012 $0.01071
Sonnet 5 $0.00005 $0.00429
Haiku 4.5 $0.00002 $0.00214

Measured 2d ago against content hash d34adfc2ee3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

configure scanned grade B with 2 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo loginctl enable-linger "$USER"

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsS --max-time 3 http://127.0.0.1:8321/health 2>/dev/null
commands/configure.md · 232 lines

How it starts

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

Purpose

Walk the user through installing semantic-search-http as a background service so every Claude Code session shares one warm indexer. Covers:

  1. Pre-flight — detect existing instances, skip or add more
  2. Tool install via uv tool install
  3. Service unit creation (launchd on macOS, systemd-user on Linux), with optional instance label for multi-instance setups
  4. MCP registration in Claude config

Process

Step 0: Pre-flight detection

Probe for an existing service:

curl -fsS --max-time 3 http://127.0.0.1:8321/health 2>/dev/null

If it returns {"status":"ok",...}, list existing service units:

  • macOS: launchctl list | grep semantic-search-http
  • Linux: systemctl --user list-units 'semantic-search-http*' --no-legend

Also check current MCP registration:

jq '.mcpServers | to_entries[] | select(.key | test("semantic"))' ~/.claude/mcp-personal.json ~/.claude.json 2>/dev/null

Report findings, then ask (single AskUserQuestion):

A semantic-search-http service is already running on port 8321 (instances: ). What would you like to do?

  1. Skip — already configured
  2. Add another instance (different port + label)
  3. Reconfigure existing instance
  • 1 (skip) → STOP with summary
  • 2 (add instance) → continue with Step 2; in Step 3 ask for instance label + alternative port
  • 3 (reconfigure) → continue with Step 2, reuse the existing label, propose unloading old plist before writing new

If no service is running, continue normally with Step 2.

Step 1: Detect platform

uname -s
  • Darwin → macOS, use launchd flow (Step 3a)
  • Linux → Linux, use systemd-user flow (Step 3b)
  • Other → STOP, report unsupported platform

Step 2: Verify, install, or upgrade the binary

Check if the binary exists:

command -v semantic-search-http || echo "MISSING"
2a: Missing → install

If missing, ask (single yes/no):

semantic-search-http not found. Install now via uv tool install (CPU-only)?

Read the full file on GitHub · 232 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. 2d ago First seen · 232 lines · 24 tokens per session scan B d34adfc2ee3b

Subscribe to this mod's changes

configure is a command published in the GitHub repository bborbe/semantic-search (2 stars, last pushed 7d ago), licensed BSD-2-Clause. It adds 24 tokens to every session and 2,143 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.