memory-mcp-1file: Command for OpenCode

.opencode/command/vida-project-analyze.md

vida-project-analyze is a command for OpenCode from pomazanbohdan/memory-mcp-1file. It costs 0 tokens per session (867 once invoked), scanned A, original, MIT.

A project-analysis command that examines stored project information and reports project health, progress speed, blockers, and trends. It can also update the project's recorded state.

In plain words
What is it for?
Use it for a full or quick health report, a health-score breakdown, velocity and trend analysis, or machine-readable JSON output.
Why use it?
It brings project status into one report instead of requiring manual review of planning files, tasks, and recent Git activity.

Command for OpenCode

Written for OpenCode: installed under .opencode/. Also seen: mentions AGENTS.md.

This is pomazanbohdan/memory-mcp-1file's own configuration. It tells OpenCode how to work on memory-mcp-1file itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything memory-mcp-1file configures →

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-project-analyze.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.

agentmods badge for vida-project-analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/pomazanbohdan/memory-mcp-1file/vida-project-analyze/github.svg)](https://agentmods.dev/commands/pomazanbohdan/memory-mcp-1file/vida-project-analyze)
Your own site
<a href="https://agentmods.dev/commands/pomazanbohdan/memory-mcp-1file/vida-project-analyze"><img src="https://agentmods.dev/badge/commands/pomazanbohdan/memory-mcp-1file/vida-project-analyze/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 vida-project-analyze

Your own site · 80×15
<a href="https://agentmods.dev/commands/pomazanbohdan/memory-mcp-1file/vida-project-analyze"><img src="https://agentmods.dev/badge/commands/pomazanbohdan/memory-mcp-1file/vida-project-analyze.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 867 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.00000 $0.00867
Opus 5.5 $0.00000 $0.00347
Sonnet 5.5 $0.00000 $0.00173
Haiku 4.5 $0.00000 $0.00087

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

Security

Grade A, and why

vida-project-analyze 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-project-analyze.md · 111 lines

How it starts

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

VIDA: PROJECT Comprehensive Analysis

Read and execute the VIDA project analysis command instructions:

@vida/commands/vida-project-analyze.md

Use @AGENTS.md for Memory Protocol context.


Syntax

/project:vida-project-analyze [OPTIONS]

OPTIONS:
  (none)         Full analysis with comprehensive report
  --quick        Fast analysis, compact output
  --json         Machine-readable JSON output
  --no-update    Analysis only, don't modify PROJECT: record
  --health-only  Show health score breakdown only
  --trends       Focus on velocity and trends analysis

Purpose

Deep analysis of PROJECT: state with health assessment, velocity tracking, and actionable recommendations. Analyzes project health from multiple dimensions and updates PROJECT: record in Memory + files.

What This Does

  1. Collects State — From State Engine (doc/state/state.yaml) OR direct artifact scanning
  2. Analyzes Health — Computes 0-100 health score based on:
    • Discovery Loop status (20 pts)
    • Epic formation rate (30 pts)
    • Implementation progress (30 pts)
    • Blocker count (20 pts)
  3. Tracks Velocity — Git commits, epic formation, task completion over 30 days
  4. Detects Trends — Accelerating, stable, or decelerating
  5. Identifies Issues — Stale items, blockers, bottlenecks
  6. Updates PROJECT — Memory MCP + _vida/README.md frontmatter
  7. Recommends Next — Prioritized actions based on current state

When to Use

  • Manual: Periodic health check (weekly/biweekly)
  • Auto: After major milestones complete
  • Scheduled: After 10 tasks completed, 7 days no activity
  • Debug: When project feels stalled or unclear state

Output Modes

Default (Comprehensive Report)

/project:vida-project-analyze

Full report with all sections: overview, tech stack, progress, health breakdown, velocity, blockers, recommendations.

Quick Mode (One-Line Summary)

/project:vida-project-analyze --quick

Output: [PROJECT] mobile-odoo | Health: 76/100 Good ↗ | Epic: 1/17 (6%) | → /vida-implement T-03

Read the full file on GitHub · 111 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. 1mo ago First seen · 111 lines · 0 tokens per session scan A d542f47dd4f8

Subscribe to this mod's changes

vida-project-analyze 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 867 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.

Related

vida-project-analyze compared with commands from other repositories

vida-project-analyze next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
vida-project-analyzepomazanbohdan/memory-mcp-1fileCommand2518d agoMITA0OpenCode
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code