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/iannuttall/unclaimed/agents-mdgit clone --depth 1 https://github.com/iannuttall/unclaimedWrote 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/iannuttall/unclaimed/agents-md)<a href="https://agentmods.dev/instructions/iannuttall/unclaimed/agents-md"><img src="https://agentmods.dev/badge/instructions/iannuttall/unclaimed/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 | $0.00495 | $0.00495 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
unclaimed 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 5d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guide
What this repo is
Unclaimed is a Node.js CLI and npm package for checking single-word domain availability. It is intentionally GitHub and npm only. Do not add a marketing site unless the project owner asks for one.
Rules
- Keep the product focused on single words. Do not turn it into a general naming generator.
- Treat
unknownas unknown, never as available. - Use explicit commands such as
unclaimed checkin agents and automation. Bareunclaimedis the human TTY interface. - Preserve resumable SQLite behavior.
sweephandles new or unresolved rows;refreshrechecks old results. - Keep Ink and React lazy-loaded so headless commands do not pay the interactive UI startup cost.
- Prefer platform APIs and zero-runtime-dependency code when practical.
- Update the README and bundled skill when command behavior changes.
- Do not commit local databases, credentials, generated build output, or registrar responses.
Structure
packages/core RDAP, WHOIS classification, liveness, and bundled words
packages/cli npm package, CLI, SQLite store, registrar pricing, and skill
packages/cli/src/ui interactive Ink interface, loaded only for a bare TTY command
scripts word-corpus build and research tooling
research useful source research kept out of runtime code
The CLI injects the Node WHOIS transport into @unclaimed/core. Keep the core
resolver logic separate from the command and interactive UI.
Commands
pnpm install
pnpm unclaimed --help
pnpm unclaimed check orbit --tlds io,ai,dev
pnpm check
pnpm pack:dry-run
Use a temporary or explicit database for tests and experiments:
pnpm unclaimed stats --db /tmp/unclaimed-test.db
Do not run refresh --all casually. It can issue hundreds of thousands of live registry requests. When it is explicitly requested, the exact command is unclaimed refresh --all.
Before publishing
- Run
pnpm check. - Inspect
pnpm pack:dry-runand keep the tarball limited to the built package, README, license, and skill. - Check
unclaimed --versionmatchespackages/cli/package.json. - Confirm npm trusted publishing points at
.github/workflows/publish.yml.
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.
- 5d ago First seen · 55 lines · 495 tokens per session scan A 2c77ce869132
unclaimed AGENTS.md is an instructions file published in the GitHub repository iannuttall/unclaimed (189 stars, last pushed 15d ago), licensed MIT. It adds 495 tokens to every session, about $0.0025 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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.