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 skills add uwuclxdy/agenticat --skill name-checkgit clone --depth 1 https://github.com/uwuclxdy/agenticatWrote 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/skills/uwuclxdy/agenticat/name-check)<a href="https://agentmods.dev/skills/uwuclxdy/agenticat/name-check"><img src="https://agentmods.dev/badge/skills/uwuclxdy/agenticat/name-check/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.
<a href="https://agentmods.dev/skills/uwuclxdy/agenticat/name-check"><img src="https://agentmods.dev/badge/skills/uwuclxdy/agenticat/name-check.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00786 |
| Opus 5 | $0.00015 | $0.00393 |
| Sonnet 5 | $0.00006 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
name-check 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 yesterday.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name Check
Procedure
- Scope first (before a rename or release). Establish from context (ask if unsure):
- what the thing does, in one line
- which registries matter: crates.io, AUR, PyPI, npm, GitHub, KDE store, domain... Check only relevant registries depending on the project.
- rename cost: unpublished (cheap, anything goes) vs already public (flag every rename consequence)
- Generate 10-30 candidates. Brainstorm and balance three axes:
- explicit: name states the function (
kate-markdown-previewoverkatdown) - brandable: short, lowercase, occasionally punny (
flit,nook,perch) - user-fit: closest to the user's stated direction Mark each candidate with which axis it leans toward. Reserve companion names too when relevant (
flit+flitd+flit-mcp).
- explicit: name states the function (
- Check availability in parallel. Fan out searches (web + registry pages) per candidate:
- exact match on each relevant registry
- general web collision: existing project, product, or company with the same name in the same space
- near-collisions worth flagging (one-letter-off popular project, trademark-adjacent)
- Report as a table with these columns:
| candidate | web collision | note |
|---|
free / taken (link) / near: <what> per cell. End with one recommendation and why.
Helper
name-check.ts (same dir as the skill, requires bun) runs the deterministic registry axis in one pass to spare you the manual fetching:
bun name-check.ts <name> [<name>...] [--table] [--registry npm,crates,...] [--tld com,io]
- compact JSON by default;
--tablefor a quick scan,--listfor registry ids. - supports npm, PyPI, crates.io, RubyGems, Hackage, Go, Docker (library), Homebrew, AUR, NuGet, GitHub, plus domain availability (RDAP, DNS-confirmed on a 404).
- domain checks run only when
--registryis unset or explicitly includesdomain(e.g.--registry npm,domain). The flag is not additive by default for domains. - does not do web collision. still run that axis via WebSearch (same-space products, companies, trademarks) and fold both into the report table. Not a legal trademark search either (see Rules).
- registry read-only.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed ac2e70eadf8d
- 9d ago First seen · 51 lines · 30 tokens per session scan A 49d178de3919
name-check is a skill published in the GitHub repository uwuclxdy/agenticat (5 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 786 once invoked, about $0.0002 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 skills, from other repositories
meta-harness
Run a Meta-Harness-style optimization loop NATIVELY — automatically search over the scaffolding around a FIXED base model (memory, retrieval, context construction, prompt templates, summarization, tool-selection logic) by proposing candidate variants, scoring each on a cheap deterministic eval, and keeping a Pareto…
meta-harness-proteus
Run one iteration of proteus memory-summary evolution. Called by metaharness.py.
gbg
Convert any plan, PRD, feature idea, or brief into a sequenced goal-by-goal execution document with reviewer-gated commits — for everyday feature development, MVPs, migrations, refactors, and hardening alike. Generates a project brief, per-goal scope/tasks/acceptance criteria, an LLM-reviewer prompt (Codex/etc.), a…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".