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 pwdev-solucoes/pwdev-claude-marketplace --skill flow-maintenancegit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/flow-maintenance)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-maintenance"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-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/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-maintenance"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/flow-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.00047 | $0.00502 |
| Opus 5 | $0.00023 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
flow-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 6d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain PWDEV Flow History
Read maintenance, artifacts, audit, and safety before proposing changes.
Route
inventoryis read-only and classifies each candidate as active, complete, stale, or archivable.archivemoves only explicitly approved, verified-complete phase or quick-task directories.changelogderives a preview from real Git commits and verified Flow execution summaries.
If the request is ambiguous, begin with inventory; it does not authorize archiving.
Inventory
- Read state, active product and phase contracts, verification verdicts, memory links, migration records, and audit references.
- List exact candidate paths, classification evidence, size, dependencies, and proposed archive destination.
- Preserve config, state, context, product contracts, memory, audit data, migration records, and the active phase.
Archive
- Produce the inventory and require explicit approval for the exact source paths and destinations.
- Resolve destinations below
.planning/flow/archive/<date>/; refuse every collision instead of overwriting. - Move only approved directories whose verification verdict is
APPROVEDand which are no longer active. - Update authorized state references, then record
archivedthrough flow_audit.py when audit is enabled. - Verify that every approved source moved, every destination exists, and no unapproved path changed.
Changelog
Read actual Git history and verified Flow summaries. Use an explicit version or Unreleased, preserve existing CHANGELOG.md content, exclude fabricated or reverted work, and present a preview before writing unless the user already authorized file generation.
Constraints
- Never delete artifacts, use recursive cleanup, rewrite Git history, or archive incomplete work.
- A stale artifact is a finding, not automatically an archive candidate.
- Do not infer approval for archive targets from a general cleanup request.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 45 lines · 47 tokens per session scan A a7bd51e933a8
flow-maintenance is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 47 tokens to every session and 502 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.