A command for merging updates from the upstream Pantheon project, the original project repository, while keeping local changes.

Use it to compare local and upstream changes, identify modified files, and merge updates across agents, commands, skills, configuration, tools, and documentation.

It helps bring in newer project changes without blindly overwriting custom work made in your copy.

update — Command for Claude Code and OpenCode by ihorkatkov/pantheon

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/ihorkatkov/pantheon

Made for: Claude Code, 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/ihorkatkov/pantheon/update/github.svg)](https://agentmods.dev/commands/ihorkatkov/pantheon/update)

Your own site

<a href="https://agentmods.dev/commands/ihorkatkov/pantheon/update"><img src="https://agentmods.dev/badge/commands/ihorkatkov/pantheon/update/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/ihorkatkov/pantheon/update"><img src="https://agentmods.dev/badge/commands/ihorkatkov/pantheon/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 615 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.00013	$0.00615
Opus 5.5	$0.00005	$0.00246
Sonnet 5.5	$0.00003	$0.00123
Haiku 4.5	$0.00001	$0.00061

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

Security

Grade A, and why

update 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/commands/update.md · 79 lines

How it starts

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

/update

You are merging upstream Pantheon updates into this workspace while preserving user customizations.

Context

The user ran make update which:

Added pantheon-upstream remote pointing to github.com/ihorkatkov/pantheon
Fetched the latest pantheon-upstream/main
Detected a version mismatch between local and upstream .pantheon-version
Launched you to perform the intelligent merge

What You Do

Step 1: Understand What Changed

Compare local vs upstream:

git diff HEAD...pantheon-upstream/main --stat
git diff HEAD...pantheon-upstream/main

Categorize changes:

Agent updates: .opencode/agents/*.md
Command updates: .opencode/commands/*.md
Skill updates: .opencode/skills/**
CLI updates: pt, setup-worktree, Makefile
Config updates: .opencode/opencode.jsonc
Doc updates: README.md, docs/

Step 2: Identify User Customizations

Check which files the user has modified:

# Files user has changed since initial clone/last update
git log --all --diff-filter=M --name-only --pretty=format: -- .opencode/ pt setup-worktree Makefile | sort -u

Read current versions of modified files to understand user customizations.

Step 3: Merge Strategy

For each changed file:

Unmodified by user → Apply upstream change directly (overwrite with upstream version)

Modified by user → Smart merge:

If upstream changed mythology/role sections and user changed project-specific sections → merge both
If both changed the same section → present both versions to the user and ask which to keep
If user added new content that upstream doesn't touch → preserve user additions

New upstream files → Add directly

Deleted upstream files → Remove (notify user if they had modifications)

Step 4: Apply Changes

Apply non-conflicting changes
Present conflicts for user resolution
Update .pantheon-version to the upstream version

Step 5: Verify

Ensure all agent files are valid markdown with frontmatter
Ensure no merge artifacts (<<<<<<<, =======, >>>>>>>)
Report: what was updated, what was preserved, what needs user attention

Read the full file on GitHub · 79 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.

1mo ago First seen · 79 lines · 13 tokens per session scan A 85979130ad97

Subscribe to this mod's changes

update is a command published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 615 once invoked, about $0.0001 per session on Opus 5.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-31.

Git and workflow

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens