What is upgrade-project?

A maintenance command that detects missing or outdated project settings and selectively updates them to current development practices.

Use it to update or add workflows, Makefiles, pre-commit hooks, and other supported configuration components in an existing project.

It helps bring an older project up to date without replacing the whole setup or discarding custom changes.

upgrade-project — Command for Claude Code by athola

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/athola/claude-night-market

agentmods

npx agentmods add commands/athola/claude-night-market/upgrade-project

Made for: Claude Code.

Or install attune, the plugin that ships this one along with the rest of its 14 skills, 11 commands, 2 agents.

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/athola/claude-night-market/upgrade-project/github.svg)](https://agentmods.dev/commands/athola/claude-night-market/upgrade-project)

Your own site

<a href="https://agentmods.dev/commands/athola/claude-night-market/upgrade-project"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/upgrade-project/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/athola/claude-night-market/upgrade-project"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/upgrade-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 767 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.00015	$0.00767
Opus 5.5	$0.00006	$0.00307
Sonnet 5.5	$0.00003	$0.00153
Haiku 4.5	$0.00002	$0.00077

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

Security

Grade A, and why

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

plugins/attune/commands/upgrade-project.md · 128 lines

How it starts

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

Attune Upgrade-Project Command

Add missing configurations or update existing ones to match current best practices.

When To Use

Use this command when you need to:

Update project tooling to current standards
Add missing configurations to existing project
Upgrade specific components (Makefile, workflows, hooks)
Bring legacy project up to modern standards
Selectively update outdated configurations

When NOT To Use

Avoid this command if:

Starting new project from scratch (use /attune:project-init)
All configurations current and complete
Need full reinitialization (backup and reinitialize)
Custom configurations that shouldn't be standardized

Usage

# Interactive upgrade - shows what's missing
/attune:upgrade-project

# Upgrade specific component
/attune:upgrade-project --component workflows
/attune:upgrade-project --component makefile
/attune:upgrade-project --component pre-commit

What This Command Does

Detects project language and existing configurations
Identifies missing configurations
Offers to add/update specific components
Preserves custom modifications (merge mode)

Workflow

# 1. Detect project and show status
python3 plugins/attune/scripts/project_detector.py .

# 2. Show missing configurations
# Example output:
# Project: my-project (Python)
# ✅ .gitignore present
# ✅ pyproject.toml present
# ⚠️  Makefile outdated (from 2023, current: 2026)
# ❌ .pre-commit-config.yaml missing
# ❌ .github/workflows/typecheck.yml missing

# 3. Ask which to add/update
# Which configurations to upgrade?
#   [x] Add .pre-commit-config.yaml
#   [x] Add .github/workflows/typecheck.yml
#   [ ] Update Makefile (will preserve custom targets)

# 4. Apply selected upgrades

Components

Available components to upgrade:

makefile - Update Makefile with new targets
workflows - Add/update GitHub Actions workflows
pre-commit - Update pre-commit hook configurations
gitignore - Update .gitignore with new patterns
dependencies - Update dependency specifications

Read the full file on GitHub · 128 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 · 128 lines · 15 tokens per session scan A 2f13b462926c

Subscribe to this mod's changes

upgrade-project is a command published in the GitHub repository athola/claude-night-market (343 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 767 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-09-03.

CI and CD Claude Code Commits DevOps and cloud Git and workflow awesome-claude-code awesome-claude-skills claude-code-plugins-marketplace claude-commands claude-hooks

validate-pr-description

Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.

rjmurillo/ai-agents · 22 tokens

issue-to-mr-setup

Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.

OpenHands/extensions · 51 tokens

upgrade-project