A guided tool for checking and fixing technical SEO and website analytics problems. Technical SEO covers issues that affect whether search engines can find, understand, and load a website.

Use it to audit indexing, canonical URLs, redirects, sitemaps, analytics, page speed, and on-page SEO, then plan, apply, deploy, and verify fixes.

It turns an unclear website problem into a checked, explained, and verified set of fixes, while asking for confirmation before making changes.

searchlight — Skill for Claude Code and Codex by ajmalaksar25

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.

Any agent

npx skills add ajmalaksar25/searchlight --skill skill

Clone the repo

git clone --depth 1 https://github.com/ajmalaksar25/searchlight

Made for: Claude Code, Codex.

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/skills/ajmalaksar25/searchlight/skill/github.svg)](https://agentmods.dev/skills/ajmalaksar25/searchlight/skill)

Your own site

<a href="https://agentmods.dev/skills/ajmalaksar25/searchlight/skill"><img src="https://agentmods.dev/badge/skills/ajmalaksar25/searchlight/skill/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/skills/ajmalaksar25/searchlight/skill"><img src="https://agentmods.dev/badge/skills/ajmalaksar25/searchlight/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,484 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.00124	$0.02484
Opus 5.5	$0.00050	$0.00994
Sonnet 5.5	$0.00025	$0.00497
Haiku 4.5	$0.00012	$0.00248

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

Security

Grade A, and why

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

skill/SKILL.md · 93 lines

How it starts

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

Searchlight

Run a website from "I don't know what's wrong" to "fixed and verified", using the searchlight MCP server for data + provisioning and the agent's repo access for fixes. Meet the user where they are (beginner → pro). Never act without confirming first.

Commands

Route on the first word of the argument; everything after is context (usually a site).

Invocation	Does	Stops at
`/searchlight audit [site]`	Read-only diagnosis: detect + explain, triaged. No changes, no provisioning, no deploy.	end of §2, then offer to fix
`/searchlight setup [site]` (or no arg)	The full guided loop: interview → detect → confirm → provision → fix → deploy → verify	§5
`/searchlight fix [site]`	Assume already audited; go straight to plan → confirm → fix → deploy → verify	§5

audit is the safe default to lead with for a nervous first-time user: show them the picture, then ask whether to fix. setup / fix change real things and always confirm first.

0. Prerequisites (check, don't assume)

The searchlight MCP server must be connected. Call auth_status / setup_status.
- Not authenticated → tell them to run searchlight login --setup, or use the auth_login tool.
- For the full hands-off run, the server must be in setup mode (setupMode: true, started with --setup) and the token must include the setup scopes (re-login with --setup). --setup is self-sufficient: it turns on provisioning (GA4/GTM/verification) and Search Console writes (sitemap submit) and reports writeEnabled: true. If setupMode is false or scopes are missing, say so up front and give the exact one-time command before proposing any write/provision step — don't discover it mid-run. (For audit, read-only auth is enough; you don't need setup mode.)
If the user's site code is open in this workspace, you can apply fixes. If not (hosted CMS), you give exact instructions instead of editing.

1. Interview FIRST (ask, confirm — don't barrel ahead)

(For audit, keep this to one line: which site? Then go straight to §2 and stop after.) Ask only what you need, in plain language, and confirm before doing anything:

Which site? (list_sites; resolve an alias or pick.)
What's the goal? (rank a new site / fix indexing / add analytics / general audit.)
Analytics: do they want it? Create a new GA4 property or connect an existing one? (ga_list_properties to see what exists.) Under which account? (list_ga_accounts.) Searchlight installs the GA4 tag directly via the gtag snippet.
What do they want to track? (key events/conversions — keep it simple for beginners.)
Code in this repo, or hosted?

Read the full file on GitHub · 93 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.

2mo ago First seen · 93 lines · 124 tokens per session scan A 50b67e90a1e1

Subscribe to this mod's changes

searchlight is a skill published in the GitHub repository ajmalaksar25/searchlight (0 stars, last pushed 4mo ago), licensed MIT. It adds 124 tokens to every session and 2,484 once invoked, about $0.0005 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.

Analytics and metrics Marketing and SEO

searchlight next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
searchlightajmalaksar25/searchlight	Skill	0	4mo ago	MIT	A	124	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code