programmatic-seo-plan@1.0.0
CAUTION· static onlyPublisher claims: "Plan template pages at scale (integrations, locations, use cases, data pages) only where real search demand meets unique data for every page, with quality gates, URL and hub structure, batch rollout and spam-policy checks. Use for "programmatic SEO", "generate pages from my database", "why are my template pages not indexed"." 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 70/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: Fake instruction boundary tag. 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
- Scale / fix / stop rules: <rules>Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.No other findings across 321 lines in 2 files.
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
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim romeoseo: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.