agentmods.dev

validate

validate is a command for coding agents from opensesh/DESIGN-OPS. It costs 0 tokens per session (2,563 once invoked), scanned B, original, Apache-2.0.

A command that checks whether configured tool connections are registered and responding. Tool connections let the coding assistant communicate with external services.

In plain words
What is it for?
Use it to check all configured tools, diagnose failures and receive interactive guidance for fixing them with the optional --fix flag.
Why use it?
It helps find broken connections after setup, credential changes or environment changes, before another command fails unexpectedly.

Command

Part of the design-ops plugin — 5 skills, 13 commands shipped together

not rated 23 3mo ago B scan 0 tokens original Apache-2.0
View the source file opensesh/DESIGN-OPS
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/opensesh/design-ops/validate
Clone the repo
git clone --depth 1 https://github.com/opensesh/DESIGN-OPS

Or install design-ops, the plugin that ships this one along with the rest of its 5 skills, 13 commands.

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 validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/opensesh/design-ops/validate.svg)](https://agentmods.dev/commands/opensesh/design-ops/validate)
Your own site
<a href="https://agentmods.dev/commands/opensesh/design-ops/validate"><img src="https://agentmods.dev/badge/commands/opensesh/design-ops/validate.svg" alt="Measured on agentmods" height="20"></a>
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 2,563 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.02563
Opus 5 $0.00000 $0.01282
Sonnet 5 $0.00000 $0.00513
Haiku 4.5 $0.00000 $0.00256

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

Security

Grade B, and why

validate scanned grade B with 1 finding 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 4d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. **Check** MCP is registered in `~/.claude/settings.json`
commands/validate.md · 393 lines

How it starts

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

/design-ops:validate

Re-validate all configured tool connections. Use this to check tool status after setup, after changing API keys, or when troubleshooting connection problems.

Trigger

/design-ops:validate [--fix]

Parameters

Flag Description
(none) Check all tools and report status
--fix Check tools and guide through fixing failures interactively

Use Cases

  1. After setup — Double-check everything works before running dashboard
  2. After changing credentials — Verify new API keys or OAuth tokens work
  3. Before running dashboard — Catch issues early instead of discovering errors in dashboard
  4. When troubleshooting — Diagnose which tools are failing and why
  5. After environment changes — Verify tools still work after system updates or config changes

Workflow

Step 1: Load Configuration

  1. Read ~/.claude/design-ops-config.yaml
  2. Extract all configured tools across all pillars
  3. Skip tools marked as status: skipped

Step 2: Validate Each Tool

For each tool (not skipped):

MCP Tools (stdio)
  1. Check MCP is registered in ~/.claude/settings.json
  2. Make test call appropriate for the tool:
    • Notion: mcp__notion__API-get-self
    • GitHub: mcp__github__search_repositories with simple query
    • Linear: Query for current user
  3. Record result: success, error message, response time
MCP Tools (HTTP/OAuth)
  1. Check MCP is registered
  2. Make test call that requires authentication:
    • Google Workspace: mcp__google-workspace__list_calendars
    • Figma: mcp__figma__whoami
    • Supabase: List databases or tables
  3. Detect OAuth errors:
    • If OAuth prompt triggered → status: oauth_pending
    • If auth successful → status: connected
    • If token expired → status: oauth_expired
API Tools (direct)
  1. Check environment variable is set:
    • Notion: NOTION_API_KEY
    • Figma (legacy): FIGMA_API_TOKEN
    • GA4: GA4_PROPERTY_ID
  2. Make test API call to validate token
  3. Record result: valid, invalid, expired, missing

Read the full file on GitHub · 393 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. 4d ago First seen · 393 lines · 0 tokens per session scan B 4ec2efec6aa7

Subscribe to this mod's changes

validate is a command published in the GitHub repository opensesh/DESIGN-OPS (23 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,563 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

claude-codeclaude-code-plugindesign-toolsfigmagithubmcp
Related

Other commands, from other repositories

design-compliance

Audit or generate regulation-specific UI patterns for HIPAA, PCI DSS, or ADA compliance. Use --regulation to target a specific standard.

Adityaraj0421/naksha-studio · 36 tokens

design-tutorial

Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.

Adityaraj0421/naksha-studio · 28 tokens

design-gdpr

Design GDPR/CCPA-compliant consent flows — cookie banners, consent hierarchy, privacy controls, and data deletion request UI.

Adityaraj0421/naksha-studio · 25 tokens

design-review

Review an existing design for quality — accessibility, usability, visual consistency, content, and motion. Accepts HTML files, Figma URLs, preview servers, or screenshots for visual AI critique.

Adityaraj0421/naksha-studio · 38 tokens

design-template

Generate a production-ready web page from a curated template category. Pick a category (landing-page, dashboard, pricing, auth, blog, ecommerce, portfolio, docs, saas, or onboarding) and get a fully-built, customized HTML/CSS template — brand colors, copy, and responsive layout included.

Adityaraj0421/naksha-studio · 64 tokens

design-voice-ui

Design a voice interface — wake word flows, confirmation patterns, error recovery, screen companion layout (if hybrid), audio feedback guidelines.

Adityaraj0421/naksha-studio · 26 tokens