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.
git clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWrote 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/commands/intellegix/intellegix-code-agent-toolkit/portfolio-status)<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/portfolio-status"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/portfolio-status/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/commands/intellegix/intellegix-code-agent-toolkit/portfolio-status"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/portfolio-status.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.00000 | $0.00423 |
| Opus 5.5 | $0.00000 | $0.00169 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
portfolio-status 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 1mo 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.
What it actually says
Portfolio Status Review
Review the health of all projects in the portfolio.
Process
1. Load Portfolio Registry
Read ~/.claude/portfolio/PORTFOLIO.md and display the project table.
2. Check Velocity Constraints
# Count active feature branches across all known project directories
# Flag if >2 active branches
- List all active feature branches across T1/T2 projects
- Flag velocity violations (>2 active branches)
3. Check T1 Project Health
For each T1 project directory that exists locally:
# Check for uncommitted changes (risk flag)
git -C [project_dir] status --porcelain
# Check last commit date (stale flag if >30 days)
git -C [project_dir] log -1 --format="%ci" 2>/dev/null
4. Check T2 Project Health
For each T2 project:
- Last commit date
- Active branches
5. Flag Issues
Report any of:
- Active branches > 2 (VELOCITY VIOLATION)
- T1 projects with uncommitted changes (RISK)
- Projects with no commits in 30+ days (STALE)
- Phase mismatches (e.g., Maintenance project with feature branches)
Output Format
## Portfolio Status — [Date]
### Velocity: [OK / VIOLATION]
Active branches: [count]/2 max
[List branches if any]
### T1 Production (60%)
| Project | Status | Last Commit | Open Branches | Issues |
|---------|--------|-------------|---------------|--------|
### T2 Strategic (30%)
| Project | Status | Last Commit | Open Branches | Issues |
|---------|--------|-------------|---------------|--------|
### T3 Experimental (10%)
[Brief status — no deep checks needed]
### Flags
- [Any violations, risks, or stale projects]
### Recommended Actions
- [Actionable next steps based on findings]
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.
- 1mo ago First seen · 66 lines · 0 tokens per session scan A 1708b77524e0
portfolio-status is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 423 tokens. 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-30.
Other commands, from other repositories
cleanup
Sweep closed issues for stale labels, missing workflow state, and Project board gaps — plus prune worktrees, branches, and milestones.
adopt
Bootstrap an existing repo for ForgeDock — triage open issues, apply labels, suggest a starter milestone, and identify first /work-on candidates.
ops-standup
Morning briefing: commits, PRs, CI, blockers and priorities of the day.
work-on
Pick up a GitHub issue and run the full investigate-build-review-merge pipeline.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
github-swarm
Create a specialized swarm for GitHub repository management.