Skip to content

Stop moderating comments by hand.
Keep the ones worth keeping.

Comment moderation is a queue that only grows. Spam filters catch the obvious cases and leave a long tail of plausible-looking junk, while genuine questions from readers sit unanswered in the same list. Talos triages the queue with actual judgement about content, and can run the moment a comment is posted.

WNorthstar Studio
Howdy, Alex
An interactive walkthrough of a real Talos run. Click a prompt to start.

Why the queue never empties

Spam filters only catch the obvious

Generic praise with a link in the author URL passes most filters and still wastes your time.

Real questions get buried

A reader asking something genuinely useful sits in the same undifferentiated list as forty pieces of junk.

It is never urgent enough

So the queue reaches four hundred and then it is a project rather than a task.

What actually happens.

Trigger on the comment, not on a timer

Hook the workflow to comment posting so triage happens immediately, with cooldowns and concurrency limits preventing a flood.

Judge the content, not just the signals

Talos reads the comment against the post it was left on, which is how you tell a real question from generic filler with a link.

Act within a narrow scope

Approve, hold or spam through manage_comments. Deletion can be withheld entirely, so the worst case is a comment left pending.

Surface what needs you

Genuine questions get reported so you can reply, rather than being approved and forgotten.

The exact tools it uses.

Talos does not improvise. Each of these is a defined tool with validated inputs, a declared risk level and its own policy setting.

Hook-triggered workflows have cooldowns and concurrency limits, so a spam burst cannot trigger hundreds of simultaneous runs.

See the full tool catalog

manage_comments

Write

List, read, create, edit, moderate, trash, restore and delete comments.

get_post

Read

Load a single post or page by ID.

search_posts

Read

Keyword search across posts, pages and public post types.

manage_agent_workflow

Read

Draft and inspect scheduled or hook-triggered workflows. Drafting counts as a write.

create_report

Read

Inline structured report cards for security, SEO, health and other audits, with file and line evidence.

create_table

Read

Inline structured data tables.

Or set it once and forget it.

Any of this can become a workflow. You write the prompt, choose the trigger, and lock the permissions before it ever runs.

How workflows work

Comment triage on post

Workflow

Trigger

Hook · wp_insert_comment

Prompt

“Read the new comment and the post it was left on. If it is spam or generic filler with a promotional link, mark it as spam. If it is a genuine question, leave it pending and note it for the daily digest. If it is a normal relevant comment, approve it.”

Pre-authorized scopes

  • content:read
  • comments:moderate

Delivery

Immediate triage, with questions collected into a daily digest.

The outcome.

Triage happens on posting, not on a backlog sweep

Comments judged against the post they were left on

Deletion permission withheld — worst case is pending

Real reader questions surfaced for a reply

Before you rely on it.

What if it marks a real comment as spam?

Spam is a recoverable state in WordPress, not a deletion, so you can restore it from the comment screen. If you would rather be cautious, scope the workflow to hold rather than spam and review the held queue yourself.

Does it replace Akismet?

No, and running both is the better setup. Let your spam filter catch the high-volume obvious cases cheaply, and let Talos apply judgement to the ambiguous remainder it leaves behind.

Could a spam flood cause hundreds of AI runs?

Hook-triggered workflows enforce cooldowns and concurrency limits, and there is a site-wide rate limit of 30 runs per hour by default plus a per-run token budget. A burst gets throttled rather than billed.

Put an agent to work in WordPress.

Spend less time clicking through admin and more time moving your site forward.