agent-connector: Command for Claude Code

.claude/commands/discovery-check.md

discovery-check is a command for Claude Code from ken-jo/agent-connector. It costs 41 tokens per session (1,055 once invoked), scanned A, original, Apache-2.0.

A scheduled report command that records weekly discovery data for agent-connector.ai. It gathers search-console and Bing query metrics, bot fetches of llms.txt, npm search position, and Context7 status, then appends one factual row to a log.

In plain words
What is it for?
Use it to track impressions, clicks, search positions, discovery-related queries, URL indexing, bot access, npm rank, and Context7 availability over the previous full week.
Why use it?
It provides a consistent record of how search engines, bots, and package search expose the site. It also separates measured facts from interpretation.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code; mentions Codex.

This is ken-jo/agent-connector's own configuration. It tells Claude Code how to work on agent-connector 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 agent-connector configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ken-jo/agent-connector. 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/ken-jo/agent-connector/main/.claude/commands/discovery-check.md
Clone the repo
git clone --depth 1 https://github.com/ken-jo/agent-connector

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 discovery-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/ken-jo/agent-connector/discovery-check/github.svg)](https://agentmods.dev/commands/ken-jo/agent-connector/discovery-check)
Your own site
<a href="https://agentmods.dev/commands/ken-jo/agent-connector/discovery-check"><img src="https://agentmods.dev/badge/commands/ken-jo/agent-connector/discovery-check/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 discovery-check

Your own site · 80×15
<a href="https://agentmods.dev/commands/ken-jo/agent-connector/discovery-check"><img src="https://agentmods.dev/badge/commands/ken-jo/agent-connector/discovery-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,055 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.00041 $0.01055
Opus 5 $0.00020 $0.00528
Sonnet 5 $0.00008 $0.00211
Haiku 4.5 $0.00004 $0.00105

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

Security

Grade A, and why

discovery-check 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 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.

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/discovery-check.md · 70 lines

How it starts

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

Run the agent-discovery check for agent-connector.ai and append ONE row to docs/ops/discovery-log.md. Facts only — numbers you actually read from the tools, "n/a" where a source is unavailable, no interpretation in the row itself. Put a one-line factual note under the table only if something changed materially (a query newly ranking, a bot newly fetching llms.txt, an index status flip).

Window: the last 7 full days ending yesterday (UTC). Site property: sc-domain:agent-connector.ai (Search Console) / https://agent-connector.ai (Bing).

1. Google Search Console (gsc MCP — suganthan-gsc-mcp)

Site sc-domain:agent-connector.ai; use site_snapshot / advanced_search_analytics.

  • Total impressions, clicks, average position for the window.
  • Top 5 queries by impressions, and separately every query containing any of: mcp, agent host, agent-connector, defineconnector, publish, deploy, install — with impressions, clicks, position.
  • Index status of https://agent-connector.ai/ and https://agent-connector.ai/llms.txt (URL inspection), (inspect_url).

2. Bing Webmaster Tools (bing-webmaster MCP)

  • get_query_stats returns weekly buckets (the Date field is an epoch-ms /Date(…)/ string; the bucket dated at the window's end covers the window). Sum impressions and clicks over that bucket, and list queries from the keyword set.
  • get_crawl_stats is daily: sum CrawledPages and CrawlErrors over the window, and report the latest InIndex.
  • get_rank_and_traffic_stats and get_query_traffic_stats fail in server 1.0.2 with a pydantic dict_type error (the API returns a list); do not use them.

3. Cloudflare (cloudflare-graphql MCP)

Zone agent-connector.ai, same window, via the GraphQL Analytics API (httpRequestsAdaptiveGroups): request counts for paths /llms.txt, /llms-full.txt, /skills/agent-connector/SKILL.md, and / — grouped by clientRequestHTTPHost/path and userAgent. Report the top user agents per path, and single out these if present: ClaudeBot, Claude-User, anthropic-ai, GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, Google-Extended, Googlebot, bingbot, CCBot, Bytespider, Applebot-Extended.

Read the full file on GitHub · 70 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 · 70 lines · 41 tokens per session scan A 4ee834f9fdbd

Subscribe to this mod's changes

discovery-check is a command published in the GitHub repository ken-jo/agent-connector (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,055 once invoked, about $0.0002 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-09-06.