directory-submissions

directory-submissions is a skill for Claude Code, Codex from patrickserrano/lacquer. It costs 189 tokens per session (5,712 once invoked), scanned A, a copy of directory-submissions, MIT.

A process for submitting a software product to online directories, such as startup, SaaS, AI, agent, MCP, no-code, and review listings.

In plain words
What is it for?
Use it to choose directories, prepare positioning, and submit a product to places such as Product Hunt and other relevant software directories.
Why use it?
It helps organize directory listings as a source of website links and product discovery. It also considers whether the listings can bring potential customers rather than only visibility.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/patrickserrano/lacquer/directory-submissions
Any agent
npx skills add patrickserrano/lacquer --skill directory-submissions
Clone the repo
git clone --depth 1 https://github.com/patrickserrano/lacquer

Made for: Claude Code, Codex.

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.

agentmods badge for directory-submissions

README.md
[![agentmods](https://agentmods.dev/badge/skills/patrickserrano/lacquer/directory-submissions.svg)](https://agentmods.dev/skills/patrickserrano/lacquer/directory-submissions)
Your own site
<a href="https://agentmods.dev/skills/patrickserrano/lacquer/directory-submissions"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/directory-submissions.svg" alt="Measured on agentmods" height="20"></a>
Per session 189 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,712 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5 $0.00189 $0.05712
Opus 5 $0.00095 $0.02856
Sonnet 5 $0.00038 $0.01142
Haiku 4.5 $0.00019 $0.00571

Measured 3d ago against content hash dd08854f5cd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

directory-submissions scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

6. Once live, verify the backlink exists and is dofollow: `curl -sIL https://directory.com/your-listing | grep -i rel=`. If absent, the link is dofollow.
Origin

This is a copy

100% identical to directory-submissions — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

core/skills/directory-submissions/SKILL.md · 382 lines

How it starts

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

Directory Submissions

You are an expert in directory-driven distribution for software products. Your goal is to help the user build a compounding backlink + discovery foundation by submitting to the right directories, in the right order, with the right positioning — and to make sure that foundation actually produces leads instead of vanity backlinks.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

Directory submissions are the foundation layer of distribution — never the whole strategy. They do three things well:

  1. Pass dofollow backlinks from high domain-rating sites into your marketing pages. This raises your DR, which makes your entire site easier to rank for competitive keywords.
  2. Create discovery surface area — people browsing AI/SaaS directories are in-market buyers, not random traffic.
  3. Get cited by AI engines — ChatGPT, Claude, Perplexity, and Google AI Overviews all pull heavily from high-DR directories when answering "what's the best [category]?" queries. AI-referred traffic converts 6–27× higher than traditional search traffic.

But directories alone will not generate meaningful leads. They exist to pass link equity into the pages that DO generate leads — template galleries, comparison pages, alternative pages, blog posts. Build the destination pages first, then submit to directories so the link equity has somewhere useful to land.

The full directory catalog lives in references/directory-list.md. The positioning variant library lives in references/positioning-variations.md. The submission tracker template lives in references/submission-tracker-template.csv.


The Three Hard Rules

Rule 1: Foundation before submission

Never submit to a directory until the landing page it will link to is live, indexed, and has:

  • A single <h1> and sequential heading hierarchy — pages with clean hierarchy have 2.8× higher AI citation rates, and 87% of ChatGPT-cited pages use a single H1.
  • A real pricing page (even "free while in beta" counts — most Tier 1 directories require one).
  • Privacy policy + terms.
  • Logo assets in PNG + SVG + square 1024×1024 + favicon.
  • 5–8 real product screenshots at 1920×1080 (not marketing mockups).
  • A 60–90 second demo video — products with video on Product Hunt get 2.7× more upvotes.
  • FAQ schema markup (AI engines heavily weight FAQPage JSON-LD for answer extraction).
  • Structured data: Organization, Product, SoftwareApplication.

Read the full file on GitHub · 382 lines

Files

What ships with it

4 files 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.

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.

  1. 3d ago First seen · 382 lines · 189 tokens per session scan A dd08854f5cd1

Subscribe to this mod's changes

directory-submissions is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed today), licensed MIT. It adds 189 tokens to every session and 5,712 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to directory-submissions, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

opik

This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…

comet-ml/opik-claude-code-plugin · 84 tokens

ollama-review

Get a second opinion from a local Ollama LLM on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. No API keys needed. Use when user asks to "review with Ollama", "local code review", or "review offline".

Lykhoyda/ask-llm · 61 tokens

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

composio-community/awesome-claude-plugins · 61 tokens

swarm

Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…

Zintellix/Claude-Skills · 138 tokens

hyper-plan

Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-plan. Produces an ordered, bite-sized plan in .hyperclaude/plans/ — the input for /hyperclaude:hyper-plan-review and /hyperclaude:hyper-implement.

zeikar/hyperclaude · 70 tokens

hyper-docs-review

Use after documentation edits — typically after the documenter agent runs, or when the user invokes /hyperclaude:hyper-docs-review. Runs Codex for accuracy, drift, completeness, broken links, cross-doc inconsistencies, redundancy — NOT prose or style. Distinct from /hyperclaude:hyper-code-review (code diffs) and…

zeikar/hyperclaude · 86 tokens