directory-submissions

directory-submissions is a skill for Claude Code, Codex from mrDesign-ww/vault-os. It costs 210 tokens per session (6,504 once invoked), scanned A, a copy of directory-submissions, MIT.

A set of instructions for submitting a software product to online directories and review sites. These listings can provide product discovery and links back to the product's website.

In plain words
What is it for?
Use it to plan submissions to startup, SaaS, AI, agent, MCP, no-code, and review directories, including Product Hunt.
Why use it?
It helps organise directory choices and submissions instead of treating every listing as equally useful.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to plan submissions to startup, SaaS, AI, agent, MCP, no-code, and review directories, including Product Hunt.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mrdesign-ww/vault-os/directory-submissions
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.

Any agent
npx skills add mrDesign-ww/vault-os --skill directory-submissions
Clone the repo
git clone --depth 1 https://github.com/mrDesign-ww/vault-os

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/mrdesign-ww/vault-os/directory-submissions/github.svg)](https://agentmods.dev/skills/mrdesign-ww/vault-os/directory-submissions)
Your own site
<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/directory-submissions"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/directory-submissions/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.

agentmods 80×15 button for directory-submissions

Your own site · 80×15
<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/directory-submissions"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/directory-submissions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 210 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00210 $0.06504
Opus 5.5 $0.00084 $0.02602
Sonnet 5.5 $0.00042 $0.01301
Haiku 4.5 $0.00021 $0.00650

Measured 7d ago against content hash 3fce43d598c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 7d 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.

Fetch the listing's HTML with `curl -fsSL https://directory.com/your-listing`, or inspect its rendered DOM in a browser. `curl -I` requests headers; it cannot inspect an anchor's `href` or `rel` attributes.
Origin

This is a copy

100% identical to directory-submissions — 12 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.

shell/codex/skills/directory-submissions/SKILL.md · 403 lines

How it starts

The opening of the file, as written. The whole thing — 403 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 · 403 lines

Files

What ships with it

5 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. 7d ago Changed · +21 lines · +21 tokens per session 3fce43d598c3
  2. 1mo 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 mrDesign-ww/vault-os (2 stars, last pushed 6d ago), licensed MIT. It adds 210 tokens to every session and 6,504 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to directory-submissions, differing in 12 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens