plan-updater-skill

plan-updater-skill is a skill for OpenCode from darellchua2/opencode-config-template. It costs 35 tokens per session (2,585 once invoked), scanned A, original, Apache-2.0.

A workflow that updates a branch-specific PLAN.md file from completed development work. A branch is a separate line of work in Git, and PLAN.md records its tasks and progress.

In plain words
What is it for?
Use it to find the matching plan, tick completed tasks, connect progress to recent commits, and create a progress commit.
Why use it?
It keeps the written plan aligned with commits so the implementation history remains traceable.

Skill for OpenCode

Written for OpenCode: installed under .opencode/. Also seen: mentions subagents; mentions OpenCode.

Good fit Use it to find the matching plan, tick completed tasks, connect progress to recent commits, and create a progress commit.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/darellchua2/opencode-config-template/plan-updater-skill
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.

Any agent
npx skills add darellchua2/opencode-config-template --skill plan-updater-skill
Clone the repo
git clone --depth 1 https://github.com/darellchua2/opencode-config-template

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 plan-updater-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/plan-updater-skill.svg)](https://agentmods.dev/skills/darellchua2/opencode-config-template/plan-updater-skill)
Your own site
<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/plan-updater-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/plan-updater-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,585 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00035 $0.02585
Opus 5 $0.00017 $0.01293
Sonnet 5 $0.00007 $0.00517
Haiku 4.5 $0.00003 $0.00259

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

Security

Grade A, and why

plan-updater-skill 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 4d 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_app/.opencode/skills/plan-updater-skill/SKILL.md · 367 lines

How it starts

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

What I do

I provide automatic PLAN.md synchronization for any workflow that implements developer code:

  1. Detect Branch Reference: Extract issue/ticket number from current branch name
  2. Find PLAN File: Locate matching PLAN file in PLANS/ directory
  3. Update Progress: Mark checkboxes as complete based on recent commits
  4. Commit Changes: Commit with semantic message format
  5. Graceful Skip: Skip silently when no PLAN file exists

When to use me

Use this skill when:

  • Your subagent implements code changes (refactoring, testing, features)
  • You're about to create a PR and want PLAN.md to reflect current state
  • You've completed a significant milestone in development
  • You want to maintain traceability between commits and plans

Trigger phrases:

  • "update plan"
  • "sync plan"
  • "update PLAN.md"
  • "mark plan progress"

Subagents That Should Use This Skill

Subagent When to Invoke
pr-workflow-subagent Before creating PR (step 3.5)
code-review-subagent After completing refactoring
testing-subagent After creating tests
ticket-plan-workflow-skill After initial PLAN creation

Core Workflow

Step 1: Detect Branch Reference

Extract issue/ticket number from branch name:

Supported Branch Patterns:

  • GIT-123 - GitHub issue (preferred)
  • issue-123 - GitHub issue (legacy)
  • 123 - GitHub issue (legacy)
  • PROJECT-123 - JIRA ticket
BRANCH_NAME=$(git branch --show-current)

# GitHub pattern: GIT-123
if [[ "$BRANCH_NAME" =~ ^GIT-([0-9]+)$ ]]; then
  ISSUE_NUM="${BASH_REMATCH[1]}"
  PLAN_TYPE="github"
  PLAN_ID="$ISSUE_NUM"
fi

# Legacy GitHub pattern (backwards compatibility): issue-123 or 123
if [[ "$BRANCH_NAME" =~ ^issue-([0-9]+)$ ]] || [[ "$BRANCH_NAME" =~ ^([0-9]+)$ ]]; then
  ISSUE_NUM="${BASH_REMATCH[1]}"
  PLAN_TYPE="github"
  PLAN_ID="$ISSUE_NUM"
fi

Step 2: Find PLAN File

Locate the matching PLAN file:

# GitHub convention
GITHUB_PLAN="PLANS/PLAN-GIT-${ISSUE_NUM}.md"

# JIRA convention
JIRA_PLAN="PLANS/PLAN-${PLAN_ID}.md"

# Check which exists
if [ -f "$GITHUB_PLAN" ]; then
  PLAN_FILE="$GITHUB_PLAN"
elif [ -f "$JIRA_PLAN" ]; then
  PLAN_FILE="$JIRA_PLAN"
else
  echo "No PLAN file found for branch: $BRANCH_NAME"
  echo "Skipping PLAN.md update (graceful skip)"
  exit 0
fi

echo "Found PLAN file: $PLAN_FILE"

Read the full file on GitHub · 367 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. 4d ago First seen · 367 lines · 35 tokens per session scan A a79d4371e9ed

Subscribe to this mod's changes

plan-updater-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 2,585 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories