slime

An agent configuration whose details are stored in a slime example file. The available input does not explain what the agent does.

In plain words
What is it for?
The available input does not say what concrete jobs it supports.
Why use it?
The provided description is too thin to identify a specific problem it removes.

Agent

Install

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.

agentmods
npx agentmods add agents/skypilot-org/skypilot/slime
Clone the repo
git clone --depth 1 https://github.com/skypilot-org/skypilot
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00007
Opus 5 $0.00000 $0.00003
Sonnet 5 $0.00000 $0.00001
Haiku 4.5 $0.00000 $0.00001

Measured 3d ago against content hash ab8184def938, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slime 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.

docs/source/examples/agents/slime.md · 1 lines

What it actually says

../../generated-examples/slime.md

Changes

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.

  1. 3d ago First seen · 1 lines · 0 tokens per session scan A ab8184def938

Subscribe to this mod's changes

slime is an agent published in the GitHub repository skypilot-org/skypilot (10,546 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7 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.

Related

Other agents, from other repositories

google-colab-expert

Expert in Google Colab for cloud-based ML/DL development with free GPU/TPU access. Specializes in Colab 2025 features (Gemini AI integration, google.colab.ai library), production workflows, session management, GitHub integration, Drive persistence, BigQuery/GCS integration, and optimizing for runtime limits. Use for…

andisab/swe-marketplace · 282 tokens

reviewing-local-changes

Review the current branch's changes for code quality, test coverage, security, best practices, and product/API alignment. Use when asked to perform a code review.

streamlit/streamlit · 38 tokens

qa-testing-feature

Performs QA testing on the feature implemented in the current branch. Reads specs, docs, and API docstrings, creates a QA test plan, executes tests using Playwright against a debug server, and generates a report with found issues. Use after implementing a feature to validate it meets requirements before finalizing a…

streamlit/streamlit · 67 tokens

simplifying-local-changes

Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality. Focuses on changes in the current branch.

streamlit/streamlit · 33 tokens

fixing-pr

Automatically fix CI failures and address PR review comments for the current branch. Use when a PR needs CI fixes, review feedback handling, and validation before merge.

streamlit/streamlit · 35 tokens

AGENTS

This directory contains custom subagent definitions for Claude Code (and Cursor, which reads from this directory).

streamlit/streamlit · 0 tokens