Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/matteotitta/genesys-skillsnpx agentmods add skills/matteotitta/genesys-skills/directory-submissionsWrote 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/matteotitta/genesys-skills/directory-submissions)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/directory-submissions"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/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.
<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/directory-submissions"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/directory-submissions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 225 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00120 | $0.02977 |
| Opus 5 | $0.00060 | $0.01489 |
| Sonnet 5 | $0.00024 | $0.00595 |
| Haiku 4.5 | $0.00012 | $0.00298 |
Grade A, and why
directory-submissions 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 9d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/directory-submissions — 13-tier launch + listing playbook
Plan and execute systematic product listings across directories, review platforms, and AI-citation surfaces with the right sequence and positioning per tier. Closes the launch loop alongside /product-launch and /aeo-content.
When to invoke
- A product is launching (new or major refresh) and needs a directory rollout plan.
- A client's directory presence is sparse and a structured audit + sequenced fill-in is needed.
- A Product Hunt launch is on the calendar and the 3-week warm-up needs scoping.
- G2 / Capterra reviews are absent or stalled and the 10-in-30 protocol needs deploying.
Do NOT invoke when:
- The destination pages aren't ready (comparison pages, alternative pages, ROI calculator) — get foundations in place first.
- The product hasn't hit its first 100 users — directory submissions before product-market signal wastes the launch window.
The 3 hard rules
- Foundation before submission. Destination pages (comparison, alternative, "vs.", ROI calculator, case studies) must exist before directories link to them. Otherwise link equity flows to a generic homepage that doesn't convert.
- Destination pages before directories. Build the page the directory links to first; submit second. Reversed order leaves directory traffic landing on stub pages.
- Positioning varies by directory type. What sells on Product Hunt (founder story + visual demo) does not sell on G2 (peer validation + feature depth) or on AI-engine citation pages (factual + comparison-honest). One positioning copy doesn't fit all.
The 13-tier submission taxonomy
Submit in tier order. Each tier has different audience, mechanics, and positioning needs.
| Tier | Examples | Audience | Positioning angle |
|---|---|---|---|
| 1 — Flagship launch | Product Hunt, BetaList | Early adopters, makers | Founder story + 60-sec demo + community-relevant hook |
| 2 — General SaaS directories | SaaSHub, AlternativeTo, GetApp | Tool researchers | Feature-by-feature comparison + screenshots |
| 3 — Review platforms | G2, Capterra, TrustRadius, Software Advice | Buyers in evaluation | Peer reviews-first; 10-in-30 protocol applies |
| 4 — Comparison hubs | AlternativeTo, Slant, StackShare | Buyers comparing options | "How we differ from X" angles |
| 5 — Investor / startup databases | Crunchbase, F6S, AngelList | Investors, partner-seekers | Traction + funding-friendly positioning |
| 6 — Tech newsletter directories | TLDR, Indie Hackers, Hacker News listings | Niche operators | Founder voice + community participation |
| 7 — AI-engine citation surfaces | Perplexity-cited domains, ChatGPT-cited resources | AI-search audience | Honest comparison + structured data + GEO-optimized content |
| 8 — Industry-specific directories | (e.g., FinTech: Finovate, FintechWeekly; AdTech: AdAge tool lists) | Vertical operators | Industry-specific use case + integrations |
| 9 — Geographic directories | LocalBusiness directories, country-specific (e.g., StartupBlink UK, France Digitale) | Local market entrants | Local language + regulatory compliance |
| 10 — Maker / no-code platforms | Bubble showcase, Webflow showcase, Notion templates | Builder community | Behind-the-scenes build + remix angle |
| 11 — Integration ecosystem | Zapier App Directory, Make Integromat, Slack App Directory | Workflow-builders | Integration value + use case |
| 12 — Conference / event directories | Sponsorship logos, attendee directories | In-person network | Event-relevant offer |
| 13 — Niche vertical directories | Targeted to client niche (e.g., for FinTech: AdviserTech directories like AdviserSoftware.com) | Niche buyers | Niche-specific value prop |
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.
- 9d ago First seen · 243 lines · 120 tokens per session scan A aa466ef569a9
directory-submissions is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 2,977 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.