A command that rebuilds cached project-state views from source files and rules in a manifest. It can also check, preview, or partially regenerate that state.

Use it to synchronize project status, lead, and memory views, validate state in continuous integration, or regenerate selected fields or views.

It helps correct stale or inconsistent project information without always rebuilding everything. Check and diff modes let you inspect possible changes before applying them.

How pomazanbohdan/memory-mcp-1file configures OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to pomazanbohdan/memory-mcp-1file. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/pomazanbohdan/memory-mcp-1file/master/.opencode/command/vida-sync.md

Clone the repo

git clone --depth 1 https://github.com/pomazanbohdan/memory-mcp-1file

Made for: OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/pomazanbohdan/memory-mcp-1file/vida-sync/github.svg)](https://agentmods.dev/commands/pomazanbohdan/memory-mcp-1file/vida-sync)

Your own site

<a href="https://agentmods.dev/commands/pomazanbohdan/memory-mcp-1file/vida-sync"><img src="https://agentmods.dev/badge/commands/pomazanbohdan/memory-mcp-1file/vida-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/pomazanbohdan/memory-mcp-1file/vida-sync"><img src="https://agentmods.dev/badge/commands/pomazanbohdan/memory-mcp-1file/vida-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 210 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00210
Opus 5.5	$0.00000	$0.00084
Sonnet 5.5	$0.00000	$0.00042
Haiku 4.5	$0.00000	$0.00021

Measured 1mo ago against content hash 070ed7d1d6b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vida-sync 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 1mo 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.

.opencode/command/vida-sync.md · 34 lines

What it actually says

VIDA: State Synchronization

Read and execute the VIDA sync command instructions:

@vida/commands/vida-sync.md

Use @AGENTS.md for Memory Protocol context.

Syntax

/project:vida-sync [OPTIONS]

OPTIONS:
  (none)        Smart sync - regenerate only if stale
  --force       Force full regeneration regardless of cache
  --check       Validate only, report issues, no file changes
  --diff        Show what would change without applying
  --view=NAME   Regenerate specific view only (lead|status|memory)
  --fields=X,Y  Regenerate only specific fields (partial sync)

Purpose

Regenerate project state from source artifacts using derivation rules defined in manifest.yaml. Produces cached projections for fast reads by other VIDA commands.

When to Use

Manual: When state seems out of sync
Auto: Triggered by /vida-lead when state is stale
CI/CD: With --check for validation

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.

1mo ago First seen · 34 lines · 0 tokens per session scan A 070ed7d1d6b4

Subscribe to this mod's changes

vida-sync is a command published in the GitHub repository pomazanbohdan/memory-mcp-1file (25 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 tokens. 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-09-12.

Project management

vida-sync next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vida-syncpomazanbohdan/memory-mcp-1file	Command	25	18d ago	MIT	A	0	OpenCode
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

memory-mcp-1file: Command for OpenCode