respira-workflow

respira-workflow is a skill for Claude Code from respira-press/agent-skills-wordpress. It costs 72 tokens per session (969 once invoked), scanned A, original, MIT.

A set of working rules for an AI agent editing a live WordPress site through Respira. It covers reporting changes, checking whether edits saved and rendered, and protecting published pages with drafts and snapshots.

In plain words
What is it for?
Use it when reading or changing WordPress pages, posts, or builder content through Respira. It helps agents identify the page builder, create safe draft copies, verify writes, and restore saved versions.
Why use it?
It reduces the risk of making an unverified change or overwriting a live page. It also makes long operations and the limits of the editing tools visible to the user.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the respira-wordpress-skills plugin — 56 skills shipped together

Good fit Use it when reading or changing WordPress pages, posts, or builder content through Respira. It helps agents identify the page builder, create safe draft copies, verify writes, and restore saved versions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/respira-press/agent-skills-wordpress/respira-workflow
Install

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.

Any agent
npx skills add respira-press/agent-skills-wordpress --skill respira-workflow
Clone the repo
git clone --depth 1 https://github.com/respira-press/agent-skills-wordpress

Made for: Claude Code.

Or install respira-wordpress-skills, the plugin that ships this one along with the rest of its 56 skills.

Wrote 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.

agentmods badge for respira-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/respira-workflow/github.svg)](https://agentmods.dev/skills/respira-press/agent-skills-wordpress/respira-workflow)
Your own site
<a href="https://agentmods.dev/skills/respira-press/agent-skills-wordpress/respira-workflow"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/respira-workflow/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.

agentmods 80×15 button for respira-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/respira-press/agent-skills-wordpress/respira-workflow"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/respira-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 969 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.00969
Opus 5.5 $0.00029 $0.00388
Sonnet 5.5 $0.00014 $0.00194
Haiku 4.5 $0.00007 $0.00097

Measured 5d ago against content hash 67225063a8f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

respira-workflow 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 5d 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.

skills/respira-workflow/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Respira Workflow

Respira gives an AI agent safe, structured access to a live WordPress site, in the site's own page builder format. This skill sets how you work with it. The safety rules themselves are in wordpress-editing-safety; Respira also sends them to every agent as its core rules.

What Respira does for the user

Make these visible when they are doing work. Do not market them.

  1. Page and post writes save a snapshot before they run. Restore is one call.
  2. Writes report whether they landed and rendered. partial_write, validator_warnings and render_validator_pass say whether the change saved and whether the page shows it. Those are different checks; read both.
  3. Every major page builder is written in its own format. No manual builder selection needed; respira_get_builder_info detects it.
  4. Live pages are protected. On a published page or post, Respira puts the edit on a draft duplicate unless the site owner turned on direct editing (an unpublished item is edited in place); ask before publishing it with respira_approve_duplicate, and once the person has said yes to publishing in this conversation, publish later changes they ask for when done and tell them they are live.
  5. Several sites, one session. Pass site_id on every call when more than one site is connected, so a change never lands on the wrong site.

Say what changed, not which tool ran

Work quietly and report in site terms. The user wants to know what happened to their site, not the name of the call that did it.

  • While a long operation runs, one short line: "updating the pricing table on the homepage duplicate."
  • When it is done: what changed, what you checked, and the preview link. "the headline on the homepage copy now reads 'Book a table'. the page renders it. preview: ..."
  • When something did not land, say that first, in plain words, and offer the next step.

Do not narrate each setup call, and do not ask permission for reads.

Be patient, and show it

Read the full file on GitHub · 67 lines

Changes

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.

  1. 5d ago Changed 67225063a8f1
  2. 9d ago First seen · 67 lines · 72 tokens per session scan A fb26dfe6dda1

Subscribe to this mod's changes

respira-workflow is a skill published in the GitHub repository respira-press/agent-skills-wordpress (48 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 969 once invoked, about $0.0003 per session on Opus 5.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-10-15.