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.
npx skills add darellchua2/opencode-config-template --skill plan-updater-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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.
[](https://agentmods.dev/skills/darellchua2/opencode-config-template/plan-updater-skill)<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>- NVIDIA SkillSpector pass
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.00035 | $0.02585 |
| Opus 5 | $0.00017 | $0.01293 |
| Sonnet 5 | $0.00007 | $0.00517 |
| Haiku 4.5 | $0.00003 | $0.00259 |
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.
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:
- Detect Branch Reference: Extract issue/ticket number from current branch name
- Find PLAN File: Locate matching PLAN file in
PLANS/directory - Update Progress: Mark checkboxes as complete based on recent commits
- Commit Changes: Commit with semantic message format
- 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"
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.
- 4d ago First seen · 367 lines · 35 tokens per session scan A a79d4371e9ed
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.
Other skills, from other repositories
ship
Use when ready to ship code to remote — handles direct push to main and PR-based feature branch flows. Do NOT use for partial workflows like just committing or just pushing.
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
jig-conformance-audit
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.
conformance-audit
Use to check whether a repository's history actually followed the jig procedure: conventional squash subjects, Release-Grade trailers on unreleased work, version tag format and placement, the main/develop fast-forward invariant, and a committed rubric. Read-only, exits non-zero on violations, and runs in CI.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.