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 khadinakbarlabs/shopify-app-builder --skill app-naminggit clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-builderWrote 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/khadinakbarlabs/shopify-app-builder/app-naming)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/app-naming"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-naming/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/khadinakbarlabs/shopify-app-builder/app-naming"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-naming.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.00103 | $0.04563 |
| Opus 5 | $0.00051 | $0.02282 |
| Sonnet 5 | $0.00021 | $0.00913 |
| Haiku 4.5 | $0.00010 | $0.00456 |
Grade A, and why
app-naming 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 10d 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify App Naming & Trademark Strategy
Frontmatter Triggers
When users ask:
- "What should I name my Shopify app?"
- "Is [name] a good app name?"
- "How do I check if my app name is trademarked?"
- "What naming patterns work for Shopify apps?"
- "Should I trademark my app name?"
- "Help me generate app name ideas"
- "Will Shopify reject my app name?"
Then execute this skill.
When to Use This Skill
Use this skill when:
- You've chosen a niche/problem to solve but need a name
- You want to validate naming choices before building
- You're unsure if your name will pass Shopify's review
- You're torn between multiple name options
- You want to ensure trademark safety before launch
Don't use this skill for:
- Naming internal projects (not going to Shopify App Store)
- Personal website names (different rules apply)
- Broader brand positioning (see Marketing skill instead)
The Naming Minefield: What Shopify Will Reject
Hard Rejects (Automatic Rejection)
Shopify will reject your app if the name contains:
-
"Shop" or "Shopify" (Shopify's protected trademark)
- ❌ "ShopPrinter" (Rejected)
- ❌ "Shopify Bundle Builder" (Rejected)
- ✅ "Bundle Blitz" (Approved)
-
Brand names without permission (Stripe, PayPal, Twilio, etc.)
- ❌ "Stripe Invoicer" (Rejected)
- ❌ "PayPal Direct Sync" (Rejected)
- ✅ "Invoice Pro" (Approved)
-
Generic/overused terms that confuse identity
- ❌ "Store Manager" (too generic, high competition)
- ❌ "Sales Tool" (meaningless)
- ✅ "Profit Dashboard" (specific problem, brandable)
-
Acronyms that are registered trademarks
- ❌ "CRM Pro" (CRM is trademarked in some contexts)
- ❌ "API Dashboard" (API is too generic)
- ✅ "Pipeline Manager" (clear, branded)
-
Offensive, vulgar, or discriminatory language
- ❌ Any slurs or explicit content
- ✅ Professional language only
Soft Rejects (Likely Rejection)
Shopify will likely reject if the name:
- Sounds too similar to existing apps (Judge.me vs Judge Pro vs Judge.ai)
- Research: Search "Shopify app [your proposed name]" before committing
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.
- 10d ago First seen · 472 lines · 103 tokens per session scan A c605f5260169
app-naming is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 4,563 once invoked, about $0.0005 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
ebay-search
Search eBay listings - find items, auctions, deals, and compare prices.
ulw-execute
Executes a written Prometheus work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.