Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/thisisAhsanIqbal/nextjs-seo-auditnpx agentmods add skills/thisisahsaniqbal/nextjs-seo-audit/meta-data-optimizationWrote 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/thisisahsaniqbal/nextjs-seo-audit/meta-data-optimization)<a href="https://agentmods.dev/skills/thisisahsaniqbal/nextjs-seo-audit/meta-data-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/meta-data-optimization.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.1 | $0.00050 | $0.00989 |
| Opus 5 | $0.00025 | $0.00495 |
| Sonnet 5 | $0.00010 | $0.00198 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
meta-data-optimization 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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta Data Optimization
Audit title, description, Open Graph, and Twitter Card meta tags.
Note: Canonical URLs, robots directives, and indexability checks are handled by the technical-seo skill. Do not duplicate those checks here.
1. Title tag
| Check | Rule | Status |
|---|---|---|
Missing <title> |
Critical for SEO | ❌ FAIL |
| Title < 30 characters | Too short | ⚠️ WARN |
| Title > 60 characters | May be truncated in SERPs | ⚠️ WARN |
| Title 30–60 characters | Optimal length | ✅ PASS |
| Title is ALL CAPS (and > 5 chars) | Perceived as spammy | ⚠️ WARN |
Title quality checks
- Keyword at start (position 0): ✅ PASS "Best placement"
- Keyword near start (position ≤ 20): ✅ PASS
- Keyword late (position > 20): ⚠️ WARN "Place keyword earlier"
- Separator present (
|,-,–,—,:): ✅ PASS "Good brand + keyword pattern" - Power words (best, guide, ultimate, how to, tips, review, top, free, new, proven): ✅ PASS "May improve CTR"
- Contains number: ✅ PASS "Numbers in titles can boost CTR"
2. Meta description
| Check | Rule | Status |
|---|---|---|
Missing <meta name="description"> |
Needs one for SERP snippets | ❌ FAIL |
| Description < 120 characters | Too short | ⚠️ WARN |
| Description > 160 characters | May be truncated | ⚠️ WARN |
| Description 120–160 characters | Optimal | ✅ PASS |
3. Character encoding
| Check | Status |
|---|---|
<meta charset="utf-8"> or <meta http-equiv="Content-Type"> present |
✅ PASS |
| Neither present | ⚠️ WARN "Add charset meta tag" |
4. Open Graph tags
Check for these required OG tags:
| Tag | Missing = |
|---|---|
og:title |
⚠️ WARN |
og:description |
⚠️ WARN |
og:image |
⚠️ WARN |
og:url |
⚠️ WARN |
og:type |
⚠️ WARN |
- All present → ✅ PASS "All required Open Graph tags present"
- All missing → ❌ FAIL "No Open Graph tags found — social sharing will use defaults"
OG image dimensions
If og:image exists, check for og:image:width and og:image:height:
- Both present → ✅ PASS
- Missing → ⚠️ WARN "Missing og:image:width / og:image:height"
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.
- 8d ago First seen · 98 lines · 50 tokens per session scan A aa3e9c3cd535
meta-data-optimization is a skill published in the GitHub repository thisisAhsanIqbal/nextjs-seo-audit (7 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 989 once invoked, about $0.0003 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-31.
Other skills, from other repositories
wgm
Autonomous build skill that turns a rough request into working software through a relentless requirements interview (grill), a persistent plan, and a Ralph-style build loop (analyze → implement → validate → review → record). Use when the user runs /wgm, or asks to build, implement, prototype, or ship a feature or app…
rugged
Companion review skill that stress-tests a request, spec, plan, diff, or system against the operators and environment that will actually run it, not an idealized one. Runs a disciplined lifecycle (Triage -> Context -> Bottleneck decomposition -> Simplify -> Field test -> Verdict) and emits exactly one of three…
teach-me
Companion learning skill that makes a codebase legible fast. Surveys a repository, builds a cited map, runs a guided tour in dependency order, and finishes with a validated first change so the learner has actually moved the code. Use when the user runs /teach-me, or asks to learn, understand, onboard onto, get up to…
podlite-markup
Create and edit Podlite markup files. Use when working with .podlite files, or when the user mentions Podlite, formatting codes, declarative blocks, structured markup for documentation, or AI agent instructions.
podlite-verify
Validate, lint, and self-check Podlite markup. Use after generating or editing .podlite files, when asked to verify/validate/lint/check Podlite, or to catch structural errors (unbalanced =begin/=end, attribute syntax, nested angles, list nesting) before delivering output.
quiz-me
Companion assessment skill that grills a user on a codebase until their understanding is proven rather than assumed. Asks one question at a time, grades every answer against the real code with citations, scores 0-100 by difficulty tier, and drills the weak areas it finds. Use when the user runs /quiz-me, or asks to be…