directory-submissions@1.0.0
CAUTION· static onlyPublisher claims: "When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Rule modification attempt; Rule modification attempt; Rule modification attempt. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…ies for $99?", "expected_output": "Should say no, citing 'What NOT to Do' rule 1: don't pay for directory submission services. Should explain the whole point is …Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.…against treating submissions as the strategy. Should reference 'What NOT to Do' rule 11: don't over-index on launch spike. Flywheel is templates + alternatives + review…Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.### Rule 2: Destination pages before directoriesFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule 3: Positioning varies by directory typeFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule 1: Foundation before submissionFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…ion into every directory?", "expected_output": "Should refuse and explain Rule 3: positioning varies by directory type. Should explain AI engines penalize duplic…Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim coreyhaines31: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.