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/onpage-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/onpage-optimization)<a href="https://agentmods.dev/skills/thisisahsaniqbal/nextjs-seo-audit/onpage-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/onpage-optimization/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/onpage-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/onpage-optimization.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.00034 | $0.00951 |
| Opus 5 | $0.00017 | $0.00476 |
| Sonnet 5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
onpage-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 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
On-Page Optimization
Analyse the HTML page for heading structure, keyword usage, and link health.
Note: This skill owns internal link analysis. For external/outbound link strategy (dofollow/nofollow, anchor text quality, domain diversity), see the backlink-monitoring skill.
1. Heading validation
Check all <h1> through <h6> elements:
| Check | Status | Rule |
|---|---|---|
| No headings at all | ❌ FAIL | Every page must have at least one heading |
No <h1> tag |
❌ FAIL | Every page must have exactly one <h1> |
Multiple <h1> tags |
⚠️ WARN | Recommend a single <h1> per page |
| Hierarchy skipped (e.g. H2 → H4) | ⚠️ WARN | Headings should follow sequential order: H1 → H2 → H3 |
| Empty heading (no text content) | ❌ FAIL | All headings must have descriptive text |
| Single H1, proper hierarchy | ✅ PASS | Heading structure is correct |
2. Keyword analysis
If a target keyword is provided, check its usage across the page:
Keyword density
- Calculate:
(keyword_count / total_words) × 100 - Ideal range: 1.0–3.0%
- Below 1.0% → ⚠️ WARN "Keyword density is low"
- Above 3.0% → ❌ FAIL "Keyword stuffing detected"
- Within range → ✅ PASS
Keyword placement — check all of these:
| Location | How to check | Missing = |
|---|---|---|
<title> tag |
Does the title contain the keyword? | ⚠️ WARN |
<h1> tag |
Does the H1 text contain the keyword? | ⚠️ WARN |
| Meta description | Does <meta name="description"> contain the keyword? |
⚠️ WARN |
First <p> tag |
Does the first paragraph contain the keyword? | ⚠️ WARN |
| Image alt text | Does any <img alt="..."> contain the keyword? |
⚠️ WARN |
Title keyword position
- Keyword at position 0 (start of title) → ✅ PASS "Best placement"
- Keyword at position ≤ 20 → ✅ PASS "Near the start"
- Keyword at position > 20 → ⚠️ WARN "Place it earlier for better ranking"
3. Link analysis
Examine all <a href="..."> elements:
Classify links
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 · 87 lines · 34 tokens per session scan A 22ef5451c0b9
onpage-optimization is a skill published in the GitHub repository thisisAhsanIqbal/nextjs-seo-audit (7 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 951 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…