Borrowing it
Nothing to install: this file belongs to WYRE-AI/autotask-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WYRE-AI/autotask-mcp/main/.claude/commands/tm/models/setup-models.mdgit clone --depth 1 https://github.com/WYRE-AI/autotask-mcpWrote 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/wyre-ai/autotask-mcp/setup-models)<a href="https://agentmods.dev/commands/wyre-ai/autotask-mcp/setup-models"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/setup-models/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/wyre-ai/autotask-mcp/setup-models"><img src="https://agentmods.dev/badge/commands/wyre-ai/autotask-mcp/setup-models.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.00245 |
| Opus 5.5 | $0.00000 | $0.00098 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
setup-models 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.
Copies of this mod
7 near-identical copies found in the catalogue:
- setup-models — 100% identical, 6 lines differ
- setup-models — 100% identical, 6 lines differ
- setup-models — 100% identical, 0 lines differ
- setup-models — 100% identical, 0 lines differ
- setup-models — 100% identical, 0 lines differ
- setup-models — 100% identical, 0 lines differ
- setup-models — 97% identical, 1 lines differ
What it actually says
Run interactive setup to configure AI models.
Interactive Model Configuration
Guides you through setting up AI providers for Task Master.
Execution
task-master models --setup
Setup Process
-
Environment Check
- Detect existing API keys
- Show current configuration
- Identify missing providers
-
Provider Selection
- Choose main provider (required)
- Select research provider (recommended)
- Configure fallback (optional)
-
API Key Configuration
- Prompt for missing keys
- Validate key format
- Test connectivity
- Save configuration
Smart Recommendations
Based on your needs:
- For best results: Claude + Perplexity
- Budget conscious: GPT-3.5 + Perplexity
- Maximum capability: GPT-4 + Perplexity + Claude fallback
Configuration Storage
Keys can be stored in:
- Environment variables (recommended)
.envfile in project- Global
.taskmaster/config
Post-Setup
After configuration:
- Test each provider
- Show usage examples
- Suggest next steps
- Verify parse-prd works
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 · 51 lines · 0 tokens per session scan A 4e7a78432bea
setup-models is a command published in the GitHub repository WYRE-AI/autotask-mcp (58 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 245 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
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
umt-doctor
Diagnose UMT MCP server setup — builds, environment variables, and config health.
umt
Survey the Universal MCP Toolkit — available servers, install state, and how to connect them to any harness.
build_dashboard
Design & build a dense SaaS dashboard or app shell — navigation, tables, empty/loading states, a generated product-UI system — not a marketing page in disguise.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.