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/hoavdc/codexkit/codexkit-portfolio-risk-radarnpx skills add hoavdc/CodexKit --skill codexkit-portfolio-risk-radargit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-portfolio-risk-radar)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-portfolio-risk-radar"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-portfolio-risk-radar.svg" alt="Measured on agentmods" 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 | $0.00073 | $0.00721 |
| Opus 5 | $0.00036 | $0.00360 |
| Sonnet 5 | $0.00015 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
codexkit-portfolio-risk-radar 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portfolio Risk Radar
Purpose
Turn scattered project updates into a portfolio-level health view that supports escalation and prioritization.
When to use
- Leadership needs a single portfolio health readout.
- A PMO needs RAID, dependency, and milestone logic across many workstreams.
- A program has conflicting status narratives and needs one truth model.
When not to use
- Only one task or one sprint is in scope.
- The request is only to reformat existing notes without analysis.
Inputs
- list of workstreams or projects
- current milestones, deadlines, and owners
- open risks, assumptions, issues, and dependencies
- status evidence, blockers, and escalation history
- material budget, scope, or capacity constraints
Procedure
- Normalize the inventory of workstreams, owners, and milestone dates.
- Separate risks, issues, assumptions, and dependencies instead of mixing them.
- Score health by schedule, scope, resourcing, dependency risk, and decision latency.
- Build a simple RAG model with explicit reasons for each rating.
- Highlight cross-project dependencies and shared bottlenecks.
- Recommend the few escalations or leadership decisions that change trajectory fastest.
- State what evidence is weak or stale.
Output
- portfolio summary with top risks and overall health
- workstream table with RAG, owner, next milestone, and escalation need
- dependency heatmap or narrative
- top decision asks and recommended owners
- next reporting rhythm
Definition of done
- Leaders can tell which workstreams are truly off-track and why.
- Escalations are prioritized, not buried in raw status text.
- Dependency risk is visible across the portfolio.
Examples
- "Turn these seven project updates into a PMO-level portfolio risk report for Monday steering."
- "We have conflicting status updates across three programs. Build a single RAID and RAG view."
Quality Criteria
- Data sources and assumptions are explicitly stated
- Calculations are reproducible from provided inputs
- Visualizations or tables have clear labels, units, and time ranges
- Caveats and confidence levels are documented for estimates
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.
- yesterday First seen · 87 lines · 73 tokens per session scan A 0f57e8156253
codexkit-portfolio-risk-radar is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 721 once invoked, about $0.0004 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
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
data_analyst
Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.
product-reviews
Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.
delivering-delegated-linear-issues
当用户明确要求领取、处理、批量清空或定时扫描 Linear 的 Delegated to Agent issue 时使用;按队列状态、领取竞争、交付路径和收尾四个阶段渐进读取。.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.