Scoped to personal/.claude/agents/ so they never load when you're working in the SGA repo. Below: each agent at a glance, plus two custom proposals for the gaps off-the-shelf agents couldn't fill.
17 agents organized into four capability domains. Each card shows what it does, when to reach for it, and what it pairs with from your existing kit. Models — opus for deep reasoning, sonnet for general work, haiku for cheap & fast.
No off-the-shelf agent fit this — every "email" agent in the awesome-claude-code repos was an enterprise marketing tool. This is the gap-filler proposal: a Microsoft Graph API + scheduled triage script that delivers a daily inbox brief and pre-drafts replies into your Outlook.
Hourly Trigger (Task Scheduler · 8am–6pm CT weekdays)
│
▼
Triage Script (Node.js)
│ uses @azure/msal-node for OAuth refresh token
▼
Microsoft Graph API (NHDPM mailbox)
│ pulls unread + last 24h read
▼
Claude Classifier (Opus 4.7)
│ classifies each message + drafts reply where needed
▼
Output Pipeline
├─ Outlook drafts created via Graph API (replies pre-written)
├─ Categories applied (urgent/action/FYI/archive) on the Outlook items
├─ HTML triage brief deployed to sga-nhdpm-inbox.pages.dev
└─ Markdown log appended to obsidian-vault/Inbox/
Mail.ReadWrite + Mail.Send + Calendars.Read (delegated)personal/.envnpm i @azure/msal-node @microsoft/microsoft-graph-clientAfter Phase 1 is stable (week 2), wrap the Graph API as an MCP server so Claude Code can interact with NHDPM inbox during sessions — "did Karen email about the bonus plan?", "draft a reply to Sarah about scheduling". Effort: +1 day.
Not budgeting — financial management. Consolidate every account into proper financial statements (Balance Sheet, P&L, Cash Flow). Track outstanding bills from companies. Detect overdue payments before they hit. Daily action briefing on what needs attention.
You don't need another budgeting app. You need treasury management for one — what every household with multiple accounts, recurring obligations, and meaningful net worth eventually wants but never builds.
Plaid Link UI (one-time setup per institution)
│
▼
Encrypted token storage (Windows DPAPI · keytar)
│
▼
Daily Sync Job (Task Scheduler · 5am CT)
├─ Plaid /transactions/sync — incremental
├─ Plaid /accounts/balance/get — current balances
├─ Plaid /liabilities/get — bills, due dates, min payments
└─ Plaid /investments/holdings — positions + values
│
▼
SQLite Local DB (NEVER deployed · personal/finance-coach/db/)
│
▼
Claude Classifier (Sonnet 4.6)
│ accounting-grade categorization
▼
Statement Generator (Opus 4.7 · monthly)
├─ Balance Sheet (net worth · by account type · 12mo trend)
├─ Income Statement (P&L · category breakdowns)
├─ Cash Flow Statement
└─ Liabilities Aging (bills due 0/7/14/30 days)
│
▼
Local HTML Dashboard (file:// · NEVER on Cloudflare)
├─ Tab: Net Worth
├─ Tab: Income & Expenses
├─ Tab: Bills Due (calendar + alerts)
├─ Tab: Investments
└─ Tab: Daily Action Briefing
keytarpersonal/finance-coach/dashboard/index.html (file://)personal/finance-coach/db/finance.sqlite (gitignored)file:// URL — never deployed to CloudflareCloned for study, not installed. Worth reading before building either of the proposals above — the orchestration patterns here directly inform how the Email Triage and Finance Coach agents should coordinate.
Location: personal/.tmp/agent-audit/agentic-workflow-patterns/
Source: ThibautMelen/agentic-workflow-patterns — curated patterns derived from Anthropic's documentation.
agents/ — reference agent implementationsfoundations/ — core concepts (single-agent loops, tool use, prompt design)guides/ — step-by-step build guidesimplementation/ — working code examplesreference/ — pattern catalogworkflows/ — multi-step workflow recipespairing-engine by formalizing how the orchestrator clones itself for parallel workworkflow-chains