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.
npx skills add T4wroot/agentic-seo --skill testimonialsgit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/testimonials)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/testimonials"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/testimonials/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/t4wroot/agentic-seo/testimonials"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/testimonials.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00084 | $0.00757 |
| Opus 5.5 | $0.00034 | $0.00303 |
| Sonnet 5.5 | $0.00017 | $0.00151 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
testimonials-generator 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 1mo 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.
This is a copy
100% identical to testimonials-generator — 88 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: Testimonials
Guides testimonial design and placement for conversion. 92% of consumers read reviews before buying; testimonials can increase conversion by up to 67%.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for customer personas and industries.
Identify:
- Content type: Text quotes, video, case studies
- Placement: Product pages, pricing, hero, dedicated page
- Audience: B2B vs B2C; industry/role relevance
Content Formats
| Format | Effectiveness | Best For |
|---|---|---|
| Video | Highest; 77% say it influences buying | Key landing pages |
| Text + photo | Versatile; easy to implement | Product, pricing |
| Case study | Deep credibility; specific outcomes | B2B, high-value |
| Star ratings | Quick trust signal | E-commerce |
Video: 95% message retention vs 10% for text.
Best Practices
Content
- Specific results: "Increased revenue by 40%" over generic praise
- Real photos and names; avoid stock images
- Variety: Different customer types, industries, use cases
- Current: Update regularly; remove outdated testimonials
Placement
- Product pages, pricing sections, near CTAs
- Filter by industry/role so prospects see relevant stories
- Organize by integration or outcome for specificity
Credibility Signals
- Company logos, job titles
- Verified reviews (badges, links)
- Links to customer profiles or live stores when possible
- Before/after narratives for emotional connection
Design Guidelines
- Clean layouts; readable typography
- Engaging visuals; avoid clutter
- Mobile-optimized; fast loading
- Carousel for multiple testimonials; see carousel for design and accessibility
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.
- 1mo ago First seen · 88 lines · 84 tokens per session scan A 6f790d09062c
testimonials-generator is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 757 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to testimonials-generator, differing in 88 lines, and is treated as a copy.
Other skills, from other repositories
seo
Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories. Use this when the user asks to "perform SEO analysis", "run SEO audit", "analyze SEO", "check technical SEO", "review schema", "Core Web Vitals", "E-E-A-T", "hreflang", "GEO", "AEO", or GitHub repository SEO optimization. For…
github
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending,"…
schema-markup
When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema…
grokipedia-recommendations
When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For multi-platform…
brand-visual-generator
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font…
image-optimization
When the user wants to optimize images for search engines and performance. Also use when the user mentions "image SEO," "alt text," "image captions," "figcaption," "image optimization," "WebP," "lazy loading," "LCP," "image sitemap," "responsive images," "srcset," "image format," or "hero image optimization." For CWV…