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 thisisAhsanIqbal/nextjs-seo-audit --skill technical-seogit clone --depth 1 https://github.com/thisisAhsanIqbal/nextjs-seo-auditWrote 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/technical-seo)<a href="https://agentmods.dev/skills/thisisahsaniqbal/nextjs-seo-audit/technical-seo"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/technical-seo/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/thisisahsaniqbal/nextjs-seo-audit/technical-seo"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/technical-seo.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.00041 | $0.01226 |
| Opus 5 | $0.00020 | $0.00613 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
technical-seo 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 10d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical SEO
Audit fundamental technical SEO factors that affect crawlability and indexability.
1. Canonical URL
| Check | Status |
|---|---|
<link rel="canonical"> missing |
⚠️ WARN "Add canonical to prevent duplicate content" |
Canonical present but empty href |
❌ FAIL |
| Canonical points to a different domain | ⚠️ WARN "Cross-domain canonical — verify this is intentional" |
| Canonical is relative (not absolute URL) | ⚠️ WARN "Use absolute URLs for canonical tags" |
| Canonical present and valid | ✅ PASS |
| Multiple canonical tags | ❌ FAIL "Only one canonical allowed per page" |
| Canonical is self-referencing | ✅ PASS (best practice) |
2. Robots meta
| Check | Status |
|---|---|
<meta name="robots" content="noindex"> |
⚠️ WARN "Page will not appear in search results" |
<meta name="robots" content="nofollow"> |
⚠️ WARN "Links on this page will not be followed" |
<meta name="robots" content="noindex, nofollow"> |
⚠️ WARN "Page excluded from search entirely" |
<meta name="robots" content="index, follow"> or absent |
✅ PASS "Page is indexable" |
<meta name="googlebot"> present |
✅ PASS — report its content |
3. Robots.txt references
Check if the page references or is affected by robots.txt:
- Look for
<meta name="robots">directives - If analysing a full site, check
robots.txtat site root for:Disallowrules that block the current pageSitemapdirective pointing to sitemap locationCrawl-delaydirectives (may slow indexing)
4. Sitemap references
| Check | Status |
|---|---|
<link rel="sitemap"> present |
✅ PASS |
| No sitemap reference found | ⚠️ WARN "Consider adding sitemap reference" |
If sitemap URL is available, verify:
- Valid XML format
- Contains the current page URL
- No URLs returning 4xx/5xx status codes
5. URL structure
Analyse the page URL (from <link rel="canonical"> or <meta property="og:url">):
| Check | Status |
|---|---|
| URL contains uppercase letters | ⚠️ WARN "Use lowercase-only URLs" |
| URL contains underscores | ⚠️ WARN "Use hyphens instead of underscores" |
URL contains special characters or spaces (encoded %20) |
⚠️ WARN "Simplify URL structure" |
| URL exceeds 100 characters | ⚠️ WARN "Keep URLs concise" |
URL has double slashes (//path) |
❌ FAIL "Fix double slashes" |
| URL has trailing slash inconsistency | ⚠️ WARN "Be consistent with trailing slashes" |
| Clean, descriptive, lowercase with hyphens | ✅ PASS |
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.
- 10d ago First seen · 117 lines · 41 tokens per session scan A 1a2ac628f340
technical-seo is a skill published in the GitHub repository thisisAhsanIqbal/nextjs-seo-audit (7 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,226 once invoked, about $0.0002 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…
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…
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…
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…