Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-codeWrote 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/commands/pwdev-solucoes/pwdev-claude-marketplace/maintenance)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/maintenance"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/maintenance/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.
<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/maintenance"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/maintenance.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.01363 |
| Opus 5 | $0.00005 | $0.00681 |
| Sonnet 5 | $0.00002 | $0.00273 |
| Haiku 4.5 | $0.00001 | $0.00136 |
Grade A, and why
maintenance 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 9d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:maintenance — Project Maintenance
Role
Utility agent for project housekeeping: archiving completed phase artifacts and generating changelogs from commit history.
Input
$ARGUMENTS: subcommand + optional arguments.
cleanup→ archive completed phase artifactschangelog→ generate CHANGELOG.md (version auto-detected)changelog 1.0.0→ generate CHANGELOG.md for a specific version- empty → show interactive menu
Procedure
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 1 — Route Subcommand
Route on $1 ($2 = optional version):
-
cleanup→ go to STEP 2 -
changelog→ go to STEP 3 ($2= optional version) -
empty → present menu:
PT-BR:
Manutencao do Projeto 1. cleanup — Arquivar artefatos de fases concluidas 2. changelog — Gerar CHANGELOG.md a partir dos commits Escolha (1-2):EN:
Project Maintenance 1. cleanup — Archive completed phase artifacts 2. changelog — Generate CHANGELOG.md from commits Choose (1-2):
STEP 2 — Artifact Cleanup
STEP 2.1 — Inventory
echo "=== PHASES ==="
ls -la .planning/phases/ 2>/dev/null
echo "=== QUICK ==="
ls -la .planning/quick/ 2>/dev/null
echo "=== CONTEXT ==="
ls -la .planning/context/ 2>/dev/null
echo "=== STATE ==="
cat .planning/state.md 2>/dev/null
echo "=== SIZE ==="
du -sh .planning/ 2>/dev/null
STEP 2.2 — Identify Archivable Items
Rules:
- Phase folders with verify/verify.md ✅ APPROVED → can be archived
- Quick tasks with summary.md ✅ → can be archived
- context/ → keep (may be consulted in the future)
- state.md → NEVER archive
- Active phase spec.md → NEVER archive (it is the active contract)
.planning/memory/→ NEVER archive (memory is durable by definition; curate it with /pwdev-code:memory forget instead)
STEP 2.3 — Ask the Human
## 🧹 Archivable Artifacts
| Artifact | Size | Status | Suggested action |
|----------|------|:------:|------------------|
| phases/{phase-slug}/ | [X]KB | ✅ Phase complete | Archive |
| quick/{slug}/ | [X]KB | ✅ Complete | Archive |
| context/ | [X]KB | 📚 Reference | Keep |
**Action:** Move archivable items to `.planning/archive/[date]/`
Confirm? (y/n)
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.
- 9d ago First seen · 197 lines · 10 tokens per session scan A 021f14474cd4
maintenance is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,363 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-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
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.
ship
Ship is the operational release-prep flow for a connected project repo.
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.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.