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 chengziyue1222/math-model-agent --skill select-modelgit clone --depth 1 https://github.com/chengziyue1222/math-model-agentWrote 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/chengziyue1222/math-model-agent/select-model)<a href="https://agentmods.dev/skills/chengziyue1222/math-model-agent/select-model"><img src="https://agentmods.dev/badge/skills/chengziyue1222/math-model-agent/select-model/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/chengziyue1222/math-model-agent/select-model"><img src="https://agentmods.dev/badge/skills/chengziyue1222/math-model-agent/select-model.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.00049 | $0.00884 |
| Opus 5.5 | $0.00020 | $0.00354 |
| Sonnet 5.5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
select-model 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Select Model
Bind each candidate, baseline and validation route to an actual evidence artifact in the existing model decision. Separate a fixed plan from a decision that observes future scenarios, and declare the scope of optimality and uncertainty before comparing them.
Include the required evidence shape in the existing decision contract: saved time series and holdout errors for forecasts, full scenario matrices for comparisons, group quantities and denominators for compositions. Specify figure fields before solving; see references/visual-evidence-plan.md when chart data affects the modeling route.
Choose a defensible route before writing code. The output is a modeling argument a reader can follow, not an algorithm label.
Workflow
- Read the complete problem; list each deliverable, object, datum, unit, objective, constraint and ambiguity.
- Decompose the problem into subproblems and draw their input/output dependencies. Mark every input as observed, externally supplied, model-derived, or unavailable. When a decision needs a future quantity and historical observations exist, explicitly compare a causal forecasting submodel with justified non-forecast alternatives before declaring the problem blocked.
- Read
references/structure-opportunity-scan.mdand inspect shared states, constraints, data, geometry, objectives and solvers. Decide explicitly whether a unified core is justified. - Use
references/model-catalog.mdto shortlist only genuinely plausible candidates for each subproblem. Compare structural fit, assumptions, identifiability, data demand, interpretability, computational cost, validation route and what would falsify each candidate; do not force a candidate count. - Prefer a route where analytical reasoning exposes structure and numerical methods resolve only the remaining unknowns. Treat reduction, symmetry, monotonicity and event functions as hypotheses requiring evidence.
- Select a primary route, a simple baseline and a validation route. For threshold search, state the monotonicity evidence or select a non-monotone alternative. For research-depth work, specify the identifiable parameters, the decision-time information and the independent experimental unit as applicable. Plan one discriminating ablation or changed-condition check where it can distinguish the claimed mechanism from an alternative. Match validation to the strength of the proposed claim: prediction accuracy, causal mechanism, feasibility, robustness and global optimality need different evidence. Specify the discriminating observation or counterexample, the artifact that will contain it, and a fallback if that evidence cannot be obtained. More metrics alone do not strengthen a claim.
- State rejected candidates and the reason each fails this problem.
- Treat the selected route as provisional until implementation and validation agree with its assumptions. If downstream evidence contradicts it, revise the selection and record which dependent artifacts must be regenerated.
What ships with it
8 files 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.
- agents/openai.yaml 246 B
- references/model-catalog.md 3.1 KB
- references/rule-pack-integration.md 646 B
- references/structure-opportunity-scan.md 2.1 KB
- references/visual-evidence-plan.md 646 B
- scripts/execute_skill.py 369 B runs code
- scripts/plan_chemical_process.py 4.0 KB runs code
- scripts/plan_problem.py 3.4 KB runs code
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.
- 3d ago Changed · +8 lines 13c1e8803741
- 1mo ago Changed · +1 lines 34d44aef218c
- 2mo ago First seen · 40 lines · 49 tokens per session scan A 4fa1cb70d14b
select-model is a skill published in the GitHub repository chengziyue1222/math-model-agent (24 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 884 once invoked, about $0.0002 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-08-30.
select-model compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| select-modelchengziyue1222/math-model-agent | Skill | 24 | 4d ago | MIT | A | 49 | Codex |
| instrument-data-to-allotropeanthropics/knowledge-work-plugins | Skill | 35k | 2d ago | Apache-2.0 | A | 123 | Claude Code |
| exploratory-data-analysisK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 83 | Claude Code |
| matlabK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 44 | Claude Code |
| phylogeneticsK-Dense-AI/scientific-agent-skills | Skill | 56k | 4d ago | MIT | A | 71 | Claude Code, Codex |
| research-engineerdavila7/claude-code-templates | Skill | 33k | yesterday | MIT | A | 43 | Claude Code, Codex |
| mapping-to-snomedmaziyarpanahi/openmed | Skill | 5.8k | yesterday | Apache-2.0 | A | 205 | Claude Code |