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/solozerolabs/namera/agents-mdgit clone --depth 1 https://github.com/solozerolabs/NameraWrote 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/solozerolabs/namera/agents-md)<a href="https://agentmods.dev/instructions/solozerolabs/namera/agents-md"><img src="https://agentmods.dev/badge/instructions/solozerolabs/namera/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.01800 | $0.01800 |
| Opus 5 | $0.00900 | $0.00900 |
| Sonnet 5 | $0.00360 | $0.00360 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
Namera 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 3d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Namera
CLI tool for checking name availability across domains, trademarks, and more. Designed to be called directly by AI agents (Codex, OpenClaw, Codex, etc.).
Tech Stack
- Python 3.10+, Click (CLI), Rich (output), httpx (HTTP)
- Build: hatchling, src layout (
src/namera/) - Tests: pytest + pytest-asyncio
Project Structure
src/namera/
cli.py # CLI entry point (Click group, 8 commands)
context.py # BusinessContext dataclass, TLD_HINTS, serialization
session.py # Interactive Q&A wizard (Rich prompts)
output.py # Multi-format rendering (JSON, NDJSON, CSV, Rich tables)
cache.py # SQLite result cache (~/.cache/namera/cache.db), per-provider TTLs
composer.py # Domain name generation from keywords + prefixes/suffixes
filters.py # Trademark risk flagging, available-only filtering
presets.py # 20 TLD presets (popular, tech, startup, fintech, geo-*, etc.)
runner.py # Async concurrent check runner with semaphore + caching
retry.py # Exponential backoff with jitter for transient errors
theme.py # Brand colors + availability styling
telemetry.py # Non-blocking session logging to Supabase
providers/
base.py # Provider ABC, ProviderResult, ProviderRegistry, CheckType enum
domain.py # DNS-based domain availability (socket.gethostbyname)
rdap.py # RDAP lookup with cascading fallbacks (RDAP → DNS → WHOIS)
whois.py # Raw socket WHOIS (port 43)
social.py # Social handle checks (GitHub, Twitter/X, Instagram)
trademark.py # Trademark provider hub (imports from trademark_supabase.py)
trademark_supabase.py # USPTO trademark lookup via Supabase Edge Function
scoring/
models.py # Signal, ScoringProfile, RankedName dataclasses
engine.py # RankingEngine: collect signals → filter → weighted score → sort
local_signals.py # Zero-cost string analysis (length, pronounceability, quality)
normalizers.py # ProviderResult → Signal conversion for each check type
profiles.py # 5 built-in profiles (default, startup-saas, fintech, consumer, developer-tools)
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.
- 3d ago First seen · 172 lines · 1,800 tokens per session scan A c96dfed9514f
Namera AGENTS.md is an instructions file published in the GitHub repository solozerolabs/Namera (4 stars, last pushed 18d ago), licensed MIT. It adds 1,800 tokens to every session, about $0.0090 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-31.
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.