agentmods.dev

wp-sync-actualizer

wp-sync-actualizer is an agent for Claude Code from TserenTserenov/FMT-exocortex-template. It costs 104 tokens per session (1,037 once invoked), scanned A, original, MIT.

A helper agent that updates a work-plan document using the actual status of related work plans. A work plan is a project record of tasks, blockers, and progress.

In plain words
What is it for?
Synchronizing open and completed phases, checking related plan changes, identifying removed blockers, and returning a patch for the main agent to apply.
Why use it?
It reduces outdated task information when related work has already changed what remains possible or necessary.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

not rated 49repo +1 today A scan 104 tokens original MIT

Good fit Synchronizing open and completed phases, checking related plan changes, identifying removed blockers, and returning a patch for the main agent to apply.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer
View source ↗ TserenTserenov/FMT-exocortex-template
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.

Clone the repo
git clone --depth 1 https://github.com/TserenTserenov/FMT-exocortex-template

Made for: Claude Code.

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 wp-sync-actualizer

README.md
[![agentmods](https://agentmods.dev/badge/agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer/github.svg)](https://agentmods.dev/agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer)
Your own site
<a href="https://agentmods.dev/agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer"><img src="https://agentmods.dev/badge/agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer/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 wp-sync-actualizer

Your own site · 80×15
<a href="https://agentmods.dev/agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer"><img src="https://agentmods.dev/badge/agents/tserentserenov/fmt-exocortex-template/wp-sync-actualizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,037 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.00104 $0.01037
Opus 5 $0.00052 $0.00518
Sonnet 5 $0.00021 $0.00207
Haiku 4.5 $0.00010 $0.00104

Measured 9d ago against content hash 224cdb263231, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wp-sync-actualizer 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 9d 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.

.claude/agents/wp-sync-actualizer.md · 86 lines

How it starts

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

WP Sync Actualizer

Ты — субагент с context isolation, задача — актуализировать контекст одного РП на основе изменений в связанных РП.

Вход

Пользователь (главный агент) передаст:

  1. Номер РП (например WP-253)
  2. Markdown bundle от scripts/wp-sync-bundle.sh с информацией о текущем РП, связанных, drift-сигналах
  3. Опционально — путь к WP-context файлу

Что делать

  1. Прочитать WP-context файл текущего РП целиком (inbox/WP-N-*.md или archive/wp-contexts/).

  2. Прочитать bundle — увидеть статусы связанных РП, их recent commits, drift-сигналы.

  3. Для каждого связанного РП с drift-сигналом:

    • Прочитать его frontmatter (Read первые 30 строк) для подтверждения статуса
    • Если sample недостаточно — прочитать секции с упоминанием той фазы/функционала, что блокирует текущий РП

  4. Определить изменения:

    • Закрытая фаза в текущем РП, ссылающаяся на связанный, который уже закрыт → проставить [x], добавить (закрыто WP-X через commit YYYY-MM-DD)
    • Открытая фаза, чей блокер снят связанным РП → проставить [x] если функционал доступен, иначе пометка unblocked: WP-X
    • Оценка времени: если бóльшая часть фаз закрыта — пересчитать budget_remaining_h пропорционально

  5. НЕ применять автоматически:

    • Если в связанных РП есть противоречие (PASS vs FAIL по той же метрике) → описать в секции «⚠️ Требует внимания» вместо применения
    • Если статус в frontmatter связанного отличается от REGISTRY → пометить как STATE_DRIFT, не закрывать ничего

  6. Вернуть unified diff через формат:

## Diff (применить через Edit tool)

Файл: `<path>`

---ORIGINAL---
<exact text для old_string>
---REPLACEMENT---
<новый текст для new_string>
---END---

(повторить для каждой правки)

## Обоснование (1 абзац)

<кратко, что и почему меняется>

## Требует внимания (если есть противоречия)

- <список конфликтов, требующих решения пользователя>

Ограничения

  • НЕ редактируй файлы напрямую — только возвращай diff в текстовом формате выше. Главный агент применит через Edit.
  • НЕ создавай новые файлы.
  • НЕ запускай git commit. Это делает главный агент.
  • НЕ делай больше 5 Read-вызовов. Если bundle недостаточен — попроси главного агента дать больше контекста.
  • НЕ выходи за рамки одного WP-context файла. Меняешь только тот РП, чей номер указан в задании.

Read the full file on GitHub · 86 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. 9d ago First seen · 86 lines · 104 tokens per session scan A 224cdb263231

Subscribe to this mod's changes

wp-sync-actualizer is an agent published in the GitHub repository TserenTserenov/FMT-exocortex-template (49 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 1,037 once invoked, about $0.0005 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.

Claude CodeProject managementagentic-workflowsai-agentsai-second-brainanthropic-claudeclaude-plugin
Related

Other agents, from other repositories

context-gathering

Use when creating a new task OR when starting/switching to a task that lacks a context manifest. ALWAYS provide the task file path so the agent can read it and update it directly with the context manifest. Skip if task file already contains "Context Manifest" section.

TeamManagementPlugin/claude-plugin · 59 tokens

scope-strategist

Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.

TeamManagementPlugin/claude-plugin · 33 tokens

cluster-intake-agent

Normalize and validate cluster refs for issue/PR dedupe runs.

vincentkoc/dotskills · 18 tokens

inventory-seeder

Read scattered findings from legacy audit folders and generate canonical 00-inventory.md rows. Used by /aidex-audit migrate after folders have been moved.

yacb2/aidex · 35 tokens

logging

Use only during context compaction or task completion. Consolidates and organizes work logs into the task's Work Log section.

TeamManagementPlugin/claude-plugin · 26 tokens

code-review

Use ONLY when explicitly requested by user or when invoked by a protocol in team-management/protocol-configs/. DO NOT use proactively. Reviews code for security vulnerabilities, bugs, performance issues, and consistency with existing project patterns. When using this agent, you must provide files and line ranges where…

TeamManagementPlugin/claude-plugin · 77 tokens