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.
npx agentmods add instructions/meepo-it/letsfinddomain-skill/agents-mdgit clone --depth 1 https://github.com/meepo-it/letsfinddomain-skillWrote 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.
[](https://agentmods.dev/instructions/meepo-it/letsfinddomain-skill/agents-md)<a href="https://agentmods.dev/instructions/meepo-it/letsfinddomain-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/meepo-it/letsfinddomain-skill/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.00709 | $0.00709 |
| Opus 5 | $0.00354 | $0.00354 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
letsfinddomain-skill AGENTS.md 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Let's Find Domain — agent instructions
Instructions for any coding agent that reads AGENTS.md (Codex, Cursor,
Copilot, Gemini CLI, Aider, Windsurf, Zed, and others).
Claude Code users: SKILL.md is the equivalent entry point, and it
loads on demand rather than staying in context.
Maintenance rules
Keep user-facing documentation bilingual
README.md and README.zh-CN.md are a pair. Any change to user-facing
workflow, installation, provider support, pricing, limits, or examples must be
made in both files in the same change.
Provider walkthroughs are also paired: every
docs/providers/*/setup.md must have a matching
setup.zh-CN.md. Keep their section order, numbered steps, environment
variables, official URLs, screenshots, and verification flow aligned. The
verification flow shown to users is /letsfinddomain-skill; do not replace it
with direct Python commands in provider walkthroughs.
Referral links, when valid and intentionally supported, belong only in the corresponding provider walkthrough link. Never add referral codes to README or invent one when the provider does not offer a confirmed program.
Run the local repository test suite after documentation or code changes:
python3 scripts/test.py
The repository includes a Git pre-commit hook under .githooks/ that runs the
same suite. Enable it once after cloning:
python3 scripts/install-hooks.py
Do not create a commit while the suite is failing. The hook is local and does not require a network connection.
User request workflow
- Start with the user's actual request. Do not run a standalone
example.compreflight before understanding the request. - Use the scripts internally and keep normal replies focused on the user's result. Do not show Python commands or a long provider survey unless the user explicitly asks for technical setup.
- If the user asks only for ideas, generate ideas without blocking on API setup.
- If availability is requested, pass the full candidate list in one batch and respect the selected provider's batch and rate limits.
- If no provider is configured, say that availability cannot be confirmed yet,
link
references/environment.md, and stop there. Do not guess or substitute a web search. - Never present
unknown,lookup failed,no RDAP for this TLD, ornot supported by this provideras available. - Always surface first-year and renewal prices when available, plus premium or renewal-cliff warnings.
- Check obvious brand collisions before recommending a name.
- Keep the tool read-only: it never buys, transfers, or changes DNS.
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.
- 6d ago First seen · 77 lines · 709 tokens per session scan A 570d5f6650ae
letsfinddomain-skill AGENTS.md is an instructions file published in the GitHub repository meepo-it/letsfinddomain-skill (273 stars, last pushed 1mo ago), licensed MIT. It adds 709 tokens to every session, about $0.0035 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.