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 greedychipmunk/agent-skills --skill elizaos-model-configuratorgit clone --depth 1 https://github.com/greedychipmunk/agent-skillsWrote 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/greedychipmunk/agent-skills/elizaos-model-configurator)<a href="https://agentmods.dev/skills/greedychipmunk/agent-skills/elizaos-model-configurator"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/elizaos-model-configurator/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/greedychipmunk/agent-skills/elizaos-model-configurator"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/elizaos-model-configurator.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.00090 | $0.01100 |
| Opus 5.5 | $0.00036 | $0.00440 |
| Sonnet 5.5 | $0.00018 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
elizaos-model-configurator 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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
elizaOS Model Configurator
Make an intentional model configuration change, not a general runtime repair or plugin implementation. Keep capability availability, data destinations, billing and actual routing explicit. Configuration is not proof of working inference.
1. Establish the target
Read project instructions, the owning README, manifest/lockfile, existing host configuration and installed model-plugin declarations. Identify core embedding, standalone agent, app/desktop, Cloud-hosted runtime or thin client. Record the resolved package versions and whether the user requested configuration only or also approved installation, restart, downloads and paid verification.
Read versions and sources. The baseline is a pinned 2.x develop snapshot, not npm's latest release. Do not silently upgrade an existing 1.x project or install a global CLI to match these examples.
2. Specify the capability plan
Fill the routing-plan template with the actual needed capabilities: text tiers, response handler/planner, embeddings, and any approved image/audio operations. It is a planning document, not runtime configuration. For each capability, record provider/model, setting names, data destination, permitted fallbacks, budget, verification and rollback. Unknowns remain unknown.
Do not assume the chat provider supplies embeddings, or that enabling one model plugin makes all capabilities available. Read provider choices. Choose only compatible, necessary plugins; reuse existing explicit host composition. Do not add a second storage adapter or duplicate registration to select a model.
3. Apply the smallest authorized change
Configure through the target host's supported settings/loader. Preserve unrelated
settings and source identities. Use the provider's actual setting names rather
than generic modelProvider or arbitrary settings.model fields.
Keep keys in approved host secret storage. Never print keys, full environment, runtime settings, connection strings or configuration dumps. Core settings and plugin environment fallback differ; inspect both. For example, current OpenAI plugin helpers can fall back to process environment even though core getSetting itself is per-agent. Do not assume that means safe multi-agent secret isolation.
What ships with it
5 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.
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.
- yesterday First seen · 103 lines · 90 tokens per session scan A 420700a9e352
elizaos-model-configurator is a skill published in the GitHub repository greedychipmunk/agent-skills (22 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,100 once invoked, about $0.0004 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-10-16.
Other skills, from other repositories
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
finetuning
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…