Governed ability
Replace in post
aafm/replace-in-post Guarded write
Literal find-and-replace inside a post's content. Sanitizes the result and edits only the body; status is never touched. Reversible via revisions.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, Replace in post ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Guarded write
Writes stay conservative, and the plugin re-checks the capability before the call runs.
- Capability gated
A connection only sees Replace in post if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys but never the values.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
In post 142, replace every 2024 with 2025.
Swap the phrase old company name for new name in post 88.
Find and replace beta with general availability in that post's body.
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for Replace in post.
Does it touch anything besides the body?
No, it edits only the content and never changes status. The result is sanitized.
Can I undo it?
Yes, it is reversible via revisions. It is also off by default, requires edit access, and is logged.
Governed by default, from the first call.
Replace in post is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.