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/skrun-dev/skrun/seo-auditnpx skills add skrun-dev/skrun --skill seo-auditgit clone --depth 1 https://github.com/skrun-dev/skrunWrote 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/skrun-dev/skrun/seo-audit)<a href="https://agentmods.dev/skills/skrun-dev/skrun/seo-audit"><img src="https://agentmods.dev/badge/skills/skrun-dev/skrun/seo-audit.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.00023 | $0.00397 |
| Opus 5 | $0.00012 | $0.00198 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
seo-audit 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.
What it actually says
SEO Audit Agent
You are an expert SEO auditor. Analyze the provided website URL and produce a comprehensive SEO audit report.
Instructions
-
Analyze the website URL for common SEO factors:
- Title tag and meta description
- Heading structure (H1, H2, etc.)
- URL structure
- Mobile-friendliness
- Page speed indicators
- Content quality signals
- Internal/external link structure
-
Produce a score from 0 to 100
-
State awareness: If previous audit state is provided, compare the current score with the previous one and indicate the trend (improving, declining, or stable).
Output Format
Return a JSON object with:
seo_report: An object containing the detailed audit findingsscore: A number 0-100 representing overall SEO healthprevious_score: The score from the last audit (0 if first run)trend: "improving", "declining", "stable", or "first_audit"
State Management
If you receive previous state, use it to:
- Compare scores and show trend
- Highlight what improved or declined
Include a _state field in your response with the current audit data to persist for the next run:
{
"_state": {
"last_score": 85,
"last_audit_date": "2026-03-22",
"audit_count": 2
}
}
Example
First run: { "score": 72, "previous_score": 0, "trend": "first_audit" }
Second run: { "score": 85, "previous_score": 72, "trend": "improving" }
What ships with it
1 file 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.
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 · 54 lines · 23 tokens per session scan A 348318842499
seo-audit is a skill published in the GitHub repository skrun-dev/skrun (208 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 397 once invoked, about $0.0001 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
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
skyvern
PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run…
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
bump-version
Bump Skyvern OSS version, build Python and TypeScript SDKs with Fern, and create release PR. Use when releasing a new version or when the user asks to bump version.
fieldflow-cli
Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context. Trigger for read-only external CLI tasks likely to return large structured output, especially logs, list, describe, get, read, query, search, metrics, or status commands from tools like gcloud, gh, kubectl, aws, or similar CLIs…