A non-binding validation command for merge-port routing configurations.

Use it to check the configuration and each upstream service, then investigate reported port or connectivity failures.

It catches invalid route syntax, occupied listening ports, and upstream services that cannot accept network connections before the proxy starts.

validate — Command for Claude Code by anivaryam/anivaryam-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/anivaryam/anivaryam-plugins

Made for: Claude Code.

Or install merge-port, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/validate/github.svg)](https://agentmods.dev/commands/anivaryam/anivaryam-plugins/validate)

Your own site

<a href="https://agentmods.dev/commands/anivaryam/anivaryam-plugins/validate"><img src="https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/validate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/anivaryam/anivaryam-plugins/validate"><img src="https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 201 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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.00201
Opus 5.5	$0.00008	$0.00080
Sonnet 5.5	$0.00004	$0.00040
Haiku 4.5	$0.00002	$0.00020

Measured 2mo ago against content hash 67300e4b760d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate 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 2mo 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.

plugins/merge-port/commands/validate.md · 12 lines

What it actually says

Run merge-port validate $ARGUMENTS.

This is a point-in-time check — it confirms the routing config parses, the listen port is currently free, and each upstream accepts TCP connections. Another process can still bind the listen port between validate and start, and an upstream that responds to TCP may still be unhealthy at HTTP layer.

After running, report each check (route syntax, listen port, each upstream) with pass/fail. If any upstream is unreachable, suggest the user start it before invoking merge-port. If the listen port is in use, identify the holder with lsof -i :<port> or ss -ltnp 'sport = :<port>' and surface the result.

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.

2mo ago First seen · 12 lines · 20 tokens per session scan A 67300e4b760d

Subscribe to this mod's changes

validate is a command published in the GitHub repository anivaryam/anivaryam-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 201 once invoked, about $0.0001 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-31.

DevOps and cloud

validate next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
validateanivaryam/anivaryam-plugins	Command	2	5mo ago	MIT	A	20	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code