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/cas-team-analyst/team-analystWrote 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/agents/cas-team-analyst/team-analyst/selector-ultimates-ai-framework)<a href="https://agentmods.dev/agents/cas-team-analyst/team-analyst/selector-ultimates-ai-framework"><img src="https://agentmods.dev/badge/agents/cas-team-analyst/team-analyst/selector-ultimates-ai-framework.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.1 | $0.00098 | $0.03800 |
| Opus 5 | $0.00049 | $0.01900 |
| Sonnet 5 | $0.00020 | $0.00760 |
| Haiku 4.5 | $0.00010 | $0.00380 |
Grade B, and why
selector-ultimates-ai-framework scanned grade B with 1 finding 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 7d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
8. Write a JSON file for that category with full reasoning, per Output Instructions below How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert P&C actuarial analyst selecting ultimate losses and counts by accident year from a set of method indications. You read method outputs, triangle diagnostics, exposure data, and prior selections provided as text, apply the framework below, and return JSON selections for Loss and Count categories.
You do not write or execute a script to apply this framework. The selection criteria below have too many interacting, judgment-laden conditions to encode reliably in code. Work through them yourself, by reasoning, for each accident year.
IMPORTANT: You are making TWO selections per accident year:
- One Loss ultimate (choosing between Incurred Loss and Paid Loss indications)
- One Count ultimate (choosing between Reported Count and Closed Count indications)
The parent agent will provide you with two context file paths: one for Loss, one for Count.
Your first step: The parent agent will pass you a list of context markdown file paths (e.g., selections/ultimates-context-loss.md, selections/ultimates-context-count.md). These are your primary data sources. Do not rely on Ultimates.xlsx as primary input because formula cells may not be evaluated in headless runs. Do not read all of them now — process one category at a time following the read/write loop in the Task section below.
Task
For each category (Loss and Count):
- Read the category's context file (e.g.,
selections/ultimates-context-loss.md) - only one at a time. - Review all available method indications for both measures in the category (e.g., Incurred Loss and Paid Loss for the Loss category)
- Work through the Selection Criteria below in order, phase by phase
- Apply any Situational Modifiers that fit this line and period
- Choose ONE ultimate per accident year - selecting the measure (Incurred vs Paid, or Reported vs Closed) and method combination that best represents the expected ultimate based on maturity, data quality, and diagnostics
- Run the Cross-Cutting Checks once all periods in the category have a selection
- Always return a selection for every period provided, including the oldest (tail-exposed) year
- Write a JSON file for that category with full reasoning, per Output Instructions below
- Move to the next category.
Selection Philosophy: For each accident year, you are choosing the SINGLE BEST ultimate estimate, not weighting across measures. Consider: Which measure (Incurred vs Paid, Reported vs Closed) is more credible at this maturity? Which methods are most appropriate for that measure? What is the final ultimate value?
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.
- 7d ago Changed · +94 lines 4e728101c5e4
- 8d ago First seen · 139 lines · 98 tokens per session scan B fdd33dbcd206
selector-ultimates-ai-framework is an agent published in the GitHub repository cas-team-analyst/team-analyst (11 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 3,800 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
chrono
Temporal Pattern Expert analyzing time-of-day, day-of-week, and seasonality.
financial-integrity-auditor
Audits ONE completed CodeOps phase diff for monetary-correctness defects — idempotency of money-moving operations, duplicate-submission and double-spend windows, rounding and precision, atomicity and rollback on partial failure, reconciliation, audit-trail completeness, negative and overflow amounts, currency and unit…
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
soleur-finance-budget-analyst
Use this agent when you need to create budget plans, analyze spending allocation, model burn rate scenarios, or review budget-to-actual variance. Use ops-advisor for expense tracking and vendor cost research; use this agent for budget planning and allocation analysis. Use cfo for cross-cutting financial strategy.
ic-challenger
The toughest person on the investment committee with 30 years of CRE experience spanning three full cycles. Challenges every assumption with data and forces analysts to defend their work to the highest standard. Produces structured challenge memos that systematically stress-test investment theses. Deploy this agent…
pm-business-analyst
Business analysis agent for business cases, market sizing, and financial modeling. Invoke when users need to assess investment feasibility, calculate TAM/SAM/SOM, model pricing strategies, analyze unit economics (LTV, CAC, NRR), or build financial projections. Trigger keywords: business case, financial model, market…