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 agentmods add skills/streamlit/agent-skills/developing-with-streamlitnpx skills add streamlit/agent-skills --skill developing-with-streamlitgit clone --depth 1 https://github.com/streamlit/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/streamlit/agent-skills/developing-with-streamlit)<a href="https://agentmods.dev/skills/streamlit/agent-skills/developing-with-streamlit"><img src="https://agentmods.dev/badge/skills/streamlit/agent-skills/developing-with-streamlit.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 | $0.00128 | $0.00405 |
| Opus 5 | $0.00064 | $0.00202 |
| Sonnet 5 | $0.00026 | $0.00081 |
| Haiku 4.5 | $0.00013 | $0.00040 |
Grade A, and why
developing-with-streamlit 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 4d 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.
This is a copy
100% identical to developing-with-streamlit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Developing with Streamlit
Streamlit (>=1.57) ships detailed reference documentation for building Streamlit apps inside its pip package. The bundled skill is a routing SKILL.md plus a references/ folder of topic-specific reference docs (dashboards, themes, layouts, session state, custom components, etc.).
Usage
Run the discovery script with the user's project directory:
python <SKILL_DIR>/scripts/discover.py --project-dir <USER_PROJECT_DIR>
The script prints either:
- A path on stdout (exit 0) — the bundled
SKILL.md. Read it; it points intoreferences/. - An
ERROR:block on stderr (non-zero exit). Follow the printed instructions and re-run.
<SKILL_DIR> is the directory containing this file; <USER_PROJECT_DIR> is the absolute path to the user's project. Passing --project-dir matters because the script resolves .venv, ../.venv, Pipfile, poetry.lock, pdm.lock, and uv.lock relative to it.
What ships with it
1 file 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.
- 4d ago First seen · 25 lines · 128 tokens per session scan A e4db5baf3eab
developing-with-streamlit is a skill published in the GitHub repository streamlit/agent-skills (224 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 128 tokens to every session and 405 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to developing-with-streamlit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…