What is namingsignal AGENTS.md?

A repository instruction file for the open-source NamingSignal clients. NamingSignal provides product-name research and checking tools through an MCP server and a command-line program.

Use it when changing the NamingSignal TypeScript and Node.js packages, their shared naming logic, or their project documentation.

It keeps agent changes aligned with repository rules, such as keeping shared code copies identical and avoiding credentials or private details in tracked files.

How moekoelueker/namingsignal configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to moekoelueker/namingsignal. 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/moekoelueker/namingsignal/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/moekoelueker/namingsignal

Made for: Codex, OpenCode.

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/instructions/moekoelueker/namingsignal/agents-md/github.svg)](https://agentmods.dev/instructions/moekoelueker/namingsignal/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/moekoelueker/namingsignal/agents-md"><img src="https://agentmods.dev/badge/instructions/moekoelueker/namingsignal/agents-md/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/instructions/moekoelueker/namingsignal/agents-md"><img src="https://agentmods.dev/badge/instructions/moekoelueker/namingsignal/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 770 This file is loaded in full into every session.

When invoked 770 The same file — it is already loaded in full.

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.00770	$0.00770
Opus 5.5	$0.00308	$0.00308
Sonnet 5.5	$0.00154	$0.00154
Haiku 4.5	$0.00077	$0.00077

Measured 19d ago against content hash 7d943cdd348d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

namingsignal 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 19d 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.

AGENTS.md · 39 lines

How it starts

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

NamingSignal open source: agent brief

The open-source clients of NamingSignal, an evidence-first product-naming service: @namingsignal/mcp (a stdio MCP server with five read-only naming tools backed by the hosted API) and @namingsignal/cli (keyless local RDAP and namespace checks, briefs, deterministic generation and decision records, plus hosted research). Both share the deterministic naming core. Status: both packages are 0.2.0 on npm (published 2026-07-14); the MCP server is com.namingsignal/naming-signal. MIT licensed. TypeScript, Node 20 or newer, npm workspaces. The hosted orchestration (model-led generation, ranking, finalist research, accounts, metering) runs at https://namingsignal.com and is not in this repository.

Hard rules

This repository is public. Tracked files hold technical notes only: no credentials, API keys, local paths, personal details or business plans.
Each package carries its own copy of the deterministic core in src/core/. Change both copies together and keep them identical: diff -r packages/cli/src/core packages/mcp/src/core must print nothing.
Registry not-found is "likely unregistered", never a purchase guarantee. A failed check, timeout or unsupported source stays unknown. Output is preliminary research, never legal advice or trademark clearance.
Never ship or log an API key. Hosted calls read NAMING_SIGNAL_API_KEY from the environment.
Publishing to npm or the MCP Registry, tagging a release or pushing needs the owner's explicit approval.
openapi.json is a static snapshot of https://namingsignal.com/openapi.json; refresh it from there.

Commands

Install: npm install
Build (must pass before a commit; there is no test suite here yet): npm run build
Pack both packages to inspect what would ship: npm run pack:all
Try the CLI after a build: node packages/cli/dist/index.js check offhook --tlds com,app --json
Publishing: there is no release workflow in this repository. Each package's prepack builds it; publish only on the owner's approval.

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

19d ago First seen · 39 lines · 770 tokens per session scan A 7d943cdd348d

Subscribe to this mod's changes

namingsignal AGENTS.md is an instructions file published in the GitHub repository moekoelueker/namingsignal (0 stars, last pushed 19d ago), licensed MIT. It adds 770 tokens to every session, about $0.0031 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-10-20.

Building agents

namingsignal AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
namingsignal AGENTS.mdmoekoelueker/namingsignal	Instructions file	0	19d ago	MIT	A	770	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

namingsignal: Instructions file for Codex