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 tomzx/agents --skill manage-portfoliogit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/manage-portfolio)<a href="https://agentmods.dev/skills/tomzx/agents/manage-portfolio"><img src="https://agentmods.dev/badge/skills/tomzx/agents/manage-portfolio/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/tomzx/agents/manage-portfolio"><img src="https://agentmods.dev/badge/skills/tomzx/agents/manage-portfolio.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.00024 | $0.00516 |
| Opus 5.5 | $0.00010 | $0.00206 |
| Sonnet 5.5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
manage-portfolio 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 22d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Portfolio
A single initiative can look healthy while the portfolio is unbalanced (too many bets in one phase, no discovery pipeline, one segment over-indexed). This skill reads all initiatives and reports portfolio-level health.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - An initialized
.pdlc/with at least a few initiatives.
Steps
- Enumerate
.pdlc/initiatives/*/and read eachprogress.mdand latest gate decision. - Compute the distribution of initiatives across the six PDLC phases. A healthy portfolio has flow: some in Discover, some in Validate, fewer in Define/Launch, and a steady Measure loop.
- Check capacity allocation against
.pdlc/context/roadmap.mdand any team capacity signal. Flag over-allocation (more Now-slot initiatives than capacity) and starvation (empty Discover pipeline). - Check bet diversity: segments, customer types, and risk levels. Flag concentration risk.
- Surface initiatives that are stuck (same phase across multiple sessions with no gate progress) — candidates for
kill-initiative. - Produce the portfolio report and recommended rebalancing actions.
Output Format
## Portfolio Health
Phase distribution: Discover 2 | Validate 1 | Define 3 | Launch 0 | Measure 4 | Killed 1
Capacity: Now-slot initiatives 5 vs capacity 3 — over-allocated by 2
Bets by segment: SMB 6 | Enterprise 1 | Developer 2 — SMB-concentrated
Stuck (>2 sessions, no gate): INIT-3, INIT-9
### Rebalancing
- Move INIT-3 and INIT-9 to kill or deprioritize (run kill-initiative)
- Shift one Define initiative back to Validate (insufficient evidence)
- Start 1-2 new Discover initiatives to refill the pipeline
Next Step
Act on the recommendations: kill-initiative for stuck bets, prioritize to rebalance the roadmap, /pdlc discover to start new initiatives.
Completion Checklist
- Phase distribution computed
- Capacity vs roadmap allocation checked
- Concentration risk assessed
- Stuck initiatives surfaced with a recommended action each
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.
- 22d ago Changed · +4 lines b386644da4a2
- 24d ago Changed d1d6a6d185c7
- 1mo ago First seen · 50 lines · 24 tokens per session scan A 2106febebde9
manage-portfolio is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 516 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.