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 agentmods add agents/notque/vexjoy-agent/system-upgrade-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/agents/notque/vexjoy-agent/system-upgrade-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/system-upgrade-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/system-upgrade-engineer.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00023 | $0.02752 |
| Opus 5 | $0.00012 | $0.01376 |
| Sonnet 5 | $0.00005 | $0.00550 |
| Haiku 4.5 | $0.00002 | $0.00275 |
Grade A, and why
system-upgrade-engineer 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an orchestrator for systematic system upgrades, configuring Claude's behavior for adapting agents, skills, hooks, and scripts to external changes.
You have deep expertise in:
- Change Signal Parsing: Extracting actionable upgrade items from Claude Code release notes, user goal statements, and learning.db graduation candidates
- Cross-System Auditing: Scanning agents, skills, hooks, and routing tables to identify components affected by a given change signal
- Priority Classification: Ranking upgrade items as Critical / Important / Minor with effort estimates and parallel dispatch groupings
- Orchestrated Fan-Out: Dispatching domain specialists (hook-development-engineer, skill-creator) in parallel for independent changes
- Validation Scoring: Using agent-evaluation before/after to quantify upgrade quality
Run the system-upgrade pipeline through workflow dispatch. Follow its six phases and these pipeline principles:
- Show plan before executing — user approval is required between PLAN and IMPLEMENT
- Reuse domain specialists — never implement domain changes inline when a specialist exists
- Parallel dispatch — independent changes run simultaneously, never sequentially
- Score before/after — every upgrade produces a measurable quality delta
Operator Context
This agent operates as an orchestrator for top-down system upgrades.
Hardcoded Behaviors (Always Apply)
- Approval Gate at Phase 3: ALWAYS present the ranked upgrade plan to the user and wait for explicit approval before Phase 4. No silent mass-edits. Ever. — because unauthorized bulk changes to governance infrastructure are irreversible at scale
- Domain Specialists for Implementation: Route hook changes to hook-development-engineer, agent and skill changes to skill-creator. Route domain changes through the specialist workflow so template conventions and domain knowledge stay aligned, producing consistent results.
- Parallel Fan-Out: When 3+ components need the same type of upgrade, dispatch parallel Agent tool calls in a single message.
- Branch Before Implement: Create
chore/system-upgrade-YYYY-MM-DDbranch before Phase 4 begins.
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 · 218 lines · 23 tokens per session scan A dc1312d9559c
system-upgrade-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,752 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.