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 AsyrafHussin/agent-skills --skill seo-best-practicesgit clone --depth 1 https://github.com/AsyrafHussin/agent-skillsWrote 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/asyrafhussin/agent-skills/seo-best-practices)<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/seo-best-practices"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/seo-best-practices/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/asyrafhussin/agent-skills/seo-best-practices"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/seo-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Prompt Injection · line 212 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00078 | $0.03261 |
| Opus 5 | $0.00039 | $0.01631 |
| Sonnet 5 | $0.00016 | $0.00652 |
| Haiku 4.5 | $0.00008 | $0.00326 |
Grade A, and why
seo-best-practices 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 11d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Best Practices
Comprehensive SEO patterns for web applications built with React and Laravel. Contains 31 rules across 8 categories covering Core Web Vitals, technical SEO, structured data, performance, social sharing, and mobile-first indexing. Supports both coding reference and audit mode.
Metadata
- Version: 1.2.0
- Scope: Laravel Blade and Laravel + Inertia.js + React
- Rule Count: 31 rules across 8 categories
- License: MIT
How to Audit
When the user asks to "audit SEO", "check SEO", or "review SEO" — run the checklist below against their codebase.
Audit Step 1: Determine Scope
- If arguments provided (
$ARGUMENTS): audit only those pages or files - If no arguments: audit all pages and layouts in the codebase
Audit Step 2: Detect Project Type
Use the detection logic in "Step 1: Detect Project Type" below to determine Laravel Blade vs Laravel + Inertia + React.
Audit Step 3: Run SEO Checklist
Work through every item below. For each, output:
- PASS — brief confirmation of what was verified
- FAIL — exact
file:line, description of the issue, and fix recommendation - N/A — if the check does not apply to this project
Core Web Vitals
- Hero/above-the-fold images use
fetchpriority="high"and are preloaded (LCP < 2.5s) - No long-running JavaScript tasks blocking interaction (INP < 200ms)
- All images and embeds have explicit
width/heightattributes (CLS < 0.1) - No dynamically injected content that shifts layout without reserved space
Technical SEO
- Every page has a unique
<title>tag (50-60 characters) - Every page has a
<meta name="description">(150-160 characters) - Every page has a
<link rel="canonical">pointing to the correct URL -
robots.txtexists and does not block important pages - XML sitemap exists and includes all indexable pages
- URLs are clean, lowercase, hyphenated — no query params for indexable pages
On-Page SEO
- One
<h1>per page containing the primary keyword - Heading hierarchy is sequential (h1 → h2 → h3) — no skipped levels
- Images have descriptive
alttext (not empty, not "image", not filename) - Internal links use descriptive anchor text (not "click here")
- Semantic HTML used (
<article>,<section>,<nav>,<main>)
What ships with it
36 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 137 KB
- metadata.json 3.8 KB
- README.md 2.0 KB
- rules/_sections.md 2.3 KB
- rules/_template.md 460 B
- rules/cwv-cls.md 4.5 KB
- rules/cwv-inp.md 4.1 KB
- rules/cwv-lcp.md 2.6 KB
- rules/mobile-content-parity.md 4.1 KB
- rules/mobile-ux.md 5.0 KB
- rules/mobile-viewport.md 3.0 KB
- rules/onpage-headings.md 2.2 KB
- rules/onpage-images.md 3.1 KB
- rules/onpage-internal-linking.md 3.2 KB
- rules/onpage-semantic-html.md 2.7 KB
- rules/perf-font-loading.md 3.1 KB
- rules/perf-image-formats.md 3.3 KB
- rules/perf-lazy-loading.md 3.1 KB
- rules/perf-resource-hints.md 3.7 KB
- rules/schema-article.md 4.8 KB
- rules/schema-breadcrumb.md 5.6 KB
- rules/schema-faq.md 5.9 KB
- rules/schema-graph.md 9.3 KB
- rules/schema-json-ld.md 4.5 KB
- rules/schema-product.md 6.1 KB
- rules/schema-validation.md 8.1 KB
- rules/social-open-graph.md 4.6 KB
- rules/social-twitter-cards.md 4.7 KB
- rules/spa-meta-management.md 4.8 KB
- rules/spa-rendering-strategy.md 4.4 KB
- rules/spa-routing.md 3.6 KB
- rules/tech-canonical-urls.md 4.8 KB
- rules/tech-meta-tags.md 5.4 KB
- rules/tech-robots-txt.md 3.7 KB
- rules/tech-sitemap-xml.md 5.5 KB
- rules/tech-url-structure.md 4.1 KB
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.
- 11d ago First seen · 348 lines · 78 tokens per session scan A 0f68b8390813
seo-best-practices is a skill published in the GitHub repository AsyrafHussin/agent-skills (75 stars, last pushed 15d ago), licensed MIT. It adds 78 tokens to every session and 3,261 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
designing-data-intensive-applications
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.
domain-driven-design-distilled
Apply Vaughn Vernon-inspired lightweight DDD rules when using bounded contexts, subdomains, context maps, and tactical modeling without excess ceremony.
implementing-domain-driven-design
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
patterns-of-enterprise-application-architecture
Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.
the-pragmatic-programmer
Apply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.