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 agentmods add skills/t4wroot/agentic-seo/logonpx skills add T4wroot/agentic-seo --skill logogit 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/logo)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/logo"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/logo.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.01220 |
| Opus 5 | $0.00039 | $0.00610 |
| Sonnet 5 | $0.00016 | $0.00244 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
logo-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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: Logo
Guides logo placement and implementation for brand recall and navigation. Logo placement affects user orientation and conversion.
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 brand guidelines and visual identity.
Brand guidelines source: Logo usage rules (clear space, minimum sizes, variants) come from branding (strategy), brand-visual-generator (visual specs), or media kit. Ensure alignment before implementation.
Identify:
- Context: Header, footer, standalone
- Platform: Web, mobile, both
- Brand guidelines: Size, clear space, variants (from brand-visual-generator or media kit)
Placement Best Practices
Optimal: Top-Left
- Brand recall: Users are 89% more likely to remember logos in top-left vs. right
- Left-aligned: ~39% brand recall vs. 21% for right-aligned
- Navigation anchor: Users expect logo to link to homepage; left placement is intuitive
- Scan pattern: Aligns with left-to-right reading flow
Avoid
- Centered logos: Users navigating home from centered logos are ~6x more likely to fail
- Right-aligned: Violates conventions; harms brand recognition
When Center May Work
- Minimal headers with few elements
- Brand-heavy landing pages where logo is focal point
- Ensure logo still links to homepage and is clearly clickable
Implementation
Linking
- Always link to homepage from logo
- Use
<a href="/">wrapping logo image - Expected behavior; don't break convention
Image
- Use appropriate format (SVG preferred for scalability)
- Provide
alttext: company/product name, not "logo" - Example:
alt="Acme Inc."notalt="Logo"
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.
- 4d ago First seen · 126 lines · 79 tokens per session scan A 226e4bf7edd2
logo-generator is a skill published in the GitHub repository T4wroot/agentic-seo (14 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 1,220 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
geo
完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料， 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 （llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。 国内和海外双市场并行：国内覆盖 智谱GLM/豆包/DeepSeek/Kimi/MiniMax/纳米AI/百度AI， 海外覆盖 Gemini/ChatGPT/Claude/Grok/Perplexity，问题库与指标按市场分开算。 当用户说「做 GEO」「生成式引擎优化」「让 AI…
fire-your-seo-agency
SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하는 스킬. 사이트를 검색엔진·답변엔진·생성 AI·네이버 AI 브리핑이 인용하는 1차 소스로 만든다. "SEO 해줘", "AI에 인용되게 해줘", "네이버 노출 늘려줘", "llms.txt 만들어줘" 류 요청에 사용. Use for "audit my site's SEO", "get my site cited by ChatGPT/Perplexity/AI Overviews", "improve search visibility", "create llms.txt", "answer engine /…
rank-audit
Full SEO/GEO/AEO/Citability/Content/Performance/Vertical/Security audit with auto-fix. Scans, reports, fixes, and verifies.
rank-aeo
Answer engine optimization. Optimize for featured snippets, voice search, People Also Ask.
rank-geo
AI search optimization audit. Optimize content for ChatGPT, Perplexity, Google AI Overviews.
rank-fix
Auto-fix all SEO/GEO/AEO findings in one command. Scan, fix, verify.