Borrowing it
Nothing to install: this file belongs to agentculture/fleet-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentculture/fleet-cli/main/.claude/skills/pypi-maintainer/SKILL.mdgit clone --depth 1 https://github.com/agentculture/fleet-cliWrote 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/agentculture/fleet-cli/pypi-maintainer)<a href="https://agentmods.dev/skills/agentculture/fleet-cli/pypi-maintainer"><img src="https://agentmods.dev/badge/skills/agentculture/fleet-cli/pypi-maintainer/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/agentculture/fleet-cli/pypi-maintainer"><img src="https://agentmods.dev/badge/skills/agentculture/fleet-cli/pypi-maintainer.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.00083 | $0.00727 |
| Opus 5.5 | $0.00033 | $0.00291 |
| Sonnet 5.5 | $0.00017 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
pypi-maintainer 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 2mo 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.
This is a copy
100% identical to pypi-maintainer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyPI Maintainer
Switch the install source for a package the agent maintains. Three sources are supported: production PyPI, TestPyPI (pre-release / dev builds), and a local editable checkout. The same script works for any package an AgentCulture sibling publishes — pass the package name as the first argument.
When to use
- Verifying a PR's TestPyPI dev build before merging.
- Reproducing a user-reported bug against the published version.
- Hot-patching against a local checkout while a fix is in flight.
- Restoring the production install after local-mode debugging.
Usage
# Production PyPI
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> pypi
# TestPyPI (pre-release dev builds)
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> test-pypi
# TestPyPI, pinned to a specific dev version
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> test-pypi --version 0.4.0.dev42
# Local editable checkout (defaults to current directory)
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> local
# Local editable from an explicit path
bash .claude/skills/pypi-maintainer/scripts/switch-source.sh <package> local --path ../<package>
Prerequisites
The script requires the following tools on PATH:
bashuv— the script delegates touv tool installanduv tool list(oruv pip installforlocal).
Why TestPyPI needs special flags
When a package is published to both PyPI and TestPyPI, uv tool install
finds the production version on PyPI first and never looks at TestPyPI.
The script passes --index-strategy unsafe-best-match so uv compares the
two index sets and picks the highest version, plus --prerelease=allow
because TestPyPI builds carry dev suffixes (e.g. 0.4.0.dev42).
After running
The script prints the resolved version once install completes — cross-check
that against the expected version (PR run number, local pyproject.toml)
before continuing.
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.
- 2mo ago First seen · 77 lines · 83 tokens per session scan A c67939b9b00e
pypi-maintainer is a skill published in the GitHub repository agentculture/fleet-cli (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 727 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pypi-maintainer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…