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 respira-press/agent-skills-wordpress --skill respira-site-auditgit clone --depth 1 https://github.com/respira-press/agent-skills-wordpressWrote 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/respira-press/agent-skills-wordpress/respira-site-audit)<a href="https://agentmods.dev/skills/respira-press/agent-skills-wordpress/respira-site-audit"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/respira-site-audit/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/respira-press/agent-skills-wordpress/respira-site-audit"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/respira-site-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01655 |
| Opus 5 | $0.00028 | $0.00827 |
| Sonnet 5 | $0.00011 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
respira-site-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 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respira Site Audit
Common Mistakes
| Mistake | Correct approach |
|---|---|
| Running analyzers without knowing which page to audit | Always confirm the target. Site-wide (all public pages) or a specific page URL or ID. |
| Reporting raw analyzer output without prioritising | Group findings by severity (CRITICAL, WARNING, SUGGESTION) and surface quick wins first. |
| Running all analyzers in sequence when only one is needed | Match the analyzer to the question. If the user asks about SEO only, run respira_analyze_seo and skip the rest. |
Skipping respira_get_builder_info before reporting element-level issues |
Builder type affects which fixes are possible. Elementor, Divi 4, Divi 5, Bricks, Beaver, and Oxygen all have different fix paths. |
| Treating AEO and SEO as interchangeable | SEO targets search rankings. AEO targets AI-generated answers. Both analyzers cover different signals and you usually want both. |
| Not checking whether the page is published before auditing | Drafts and private pages may produce incomplete results. Confirm status: publish first. |
Using extract_builder_content when you only need structure |
Use respira_get_page_outline for the "what is on this page" read. It is lighter and includes the primary heading per row. |
Inputs
- Target: a specific page URL, page ID, or "the whole site".
- Scope: which analyzers to run. Default is all eight.
- Output format: a summary for the user, or JSON for a CI / CD pipeline.
Workflow
Single-page audit
respira_get_site_context. Confirm site URL, active SEO plugin (RankMath, Yoast, AIOSEO, SEOPress), active builder, WooCommerce presence.respira_get_builder_info. Note builder type for element-level fix recommendations.respira_get_page_outlineif the structure needs to be discussed.- Run analyzers in parallel where possible:
respira_analyze_seo. Title, meta description, headings, internal links, canonical.respira_analyze_aeo. Structured content, FAQ schema, answer-box signals.respira_analyze_readability. Flesch score, sentence length, passive voice.respira_analyze_performance. Load time, image sizes, render-blocking resources.respira_scan_page_accessibility. WCAG 2.1 AA violations, alt text, contrast.respira_analyze_images. Per-image weight, format, oversize-by-X factor.respira_check_structured_data. Schema.org presence per page.respira_get_core_web_vitals. CrUX-backed LCP, INP, CLS where available.
- Aggregate findings by severity: CRITICAL → WARNING → SUGGESTION.
- Build a prioritised fix list: quick wins first (alt text, missing meta) before structural changes.
- Report: headline score per area plus top 3 fixes per area.
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 · 115 lines · 56 tokens per session scan A c676813bfe02
respira-site-audit is a skill published in the GitHub repository respira-press/agent-skills-wordpress (43 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 1,655 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-30.
Other skills, from other repositories
chatdoc-studio-api
ChatDOC Studio API usage guide - complete documentation and examples for PDF parsing, chat applications, agent applications, content retrieval, and data extraction APIs.
ChatDOC Studio--KnowledgeMate
Create and operate ChatDOC Studio knowledge bases through pdrouter using a Bearer API key and JavaScript helpers. Use when Codex needs to upload one or more PDF/DOC/DOCX files, skip failed files without aborting the whole job, create a knowledge base from successful uploads, or call the ChatDOC Studio knowledge-base…
PDFlux-PDF2Markdown
Convert unstructured documents into LLM-ready structured data. Supports PDF, Word, PPT, and images; extracts paragraphs, formulas, tables, charts, and other elements in one step; generates up to 8 levels of headings; and outputs Markdown organized in reading order. Useful for field extraction, comparison and…
Calliper-Compare2Markdown
Compare two local documents and convert differences into LLM-ready Markdown in one synchronous call. Supports PDF, Word, PPT, and image documents accepted by Calliper, and returns a structured markdown diff table suitable for change review, clause comparison, downstream extraction, and rule-based validation.
open-codex-ui
Install, update, secure, daemonize, expose through Cloudflare Tunnel, and enable speech input for the open-source Open Codex UI application. Use when a user asks to install or enable Open Codex UI, configure its login daemon, set its access password, install or manage the sherpa-onnx bilingual speech model…
query-loki-project-logs
Query Grafana Loki logs that are organized by labels such as projectname or project, env, and filename, where filename distinguishes nginx, web, worker, stdout, and stderr streams. Use when Codex needs to inspect logs with logcli, discover available projects or environments, list a project's log files, narrow to a…