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 skills/devantler-tech/agent-plugins/portfolio-maintenancenpx skills add devantler-tech/agent-plugins --skill portfolio-maintenancegit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWhat 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.00095 | $0.05776 |
| Opus 5 | $0.00048 | $0.02888 |
| Sonnet 5 | $0.00019 | $0.01155 |
| Haiku 4.5 | $0.00010 | $0.00578 |
Grade A, and why
portfolio-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 yesterday.
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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio maintenance — the run loop
This is the run procedure for an autonomous engineer that both operates a portfolio of products
(keeps CI, dependencies, and PRs healthy) and advances it (strategy, features, coverage,
performance, quality). Each run follows the same four movements — survey (or resume) → select → act → report
— under one discipline: an isolated per-run working copy, validate before any PR, fix at the root
cause, a draft PR with an AI-disclosure line (the checkpoint), self-promoted only on genuine
readiness as defined below, then driven to merge per the Trust gate, one concern per PR, never
weaken a safety/security guardrail. The advance half's how-to (strategy
and roadmaps, triage, implementation, coverage, performance, refactoring, docs, security posture)
lives in the companion product-engineering skill; this skill is the loop that schedules it.
Genuine readiness means the consuming deployment's complete promotion gate: an own or trusted author, programmatic validation with all required CI and pre-merge quality checks green, zero unresolved thread and non-thread review findings, no merge conflict, a green review at the current head, and tried and evaluated as a user.
Companion skills — install them together. This loop delegates its advance movement to
product-engineering and its learnings-distil step to self-improvement; a single-skill install
does not pull companions in automatically. Install all three from this library, or — when a
companion is absent — the corresponding movement falls back to the consuming deployment's own
AGENTS.md guidance rather than being silently skipped.
This skill is authored against the consumer contract sections defined by the consuming deployment's
AGENTS.md (per the agentic-engineering plugin's parameterization contract): the Portfolio map
(which repositories are in scope, plus each product's ## Maintenance card — validate commands,
labels, protected/generated files, roadmap home), the Trust gate (the exact logins that may be
auto-driven, which bots are reviewer-only, and the per-repo merge mechanics such as merge queues or
auto-merge automation), the Cadence (run frequency and the per-product rotation numbers for
strategy reviews, docs passes, and heavy tasks), Memory (where the durable cross-run store lives
and what cursors it holds), and Maintainer channels (how a human decision is actively reached —
e.g. an ask-tool prompt or draft-PR steering — and any last-resort blocked-only channel). Where this
skill says "per the X section", the consuming repo supplies the concrete fact.
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.
- yesterday First seen · 334 lines · 95 tokens per session scan A 73713a200e7c
portfolio-maintenance is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 95 tokens to every session and 5,776 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.