Streamlit is a Python framework that turns scripts into interactive web applications for data exploration, dashboards, reports, and chat interfaces. Data scientists, machine-learning practitioners, and developers use it to build and share data apps without implementing the web interface from scratch. The catalogue add-ons support coding-agent workflows for Streamlit applications.
Borrowing it
Nothing to install: this file belongs to streamlit/streamlit. 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/streamlit/streamlit/develop/.github/instructions/specs.instructions.mdgit clone --depth 1 https://github.com/streamlit/streamlitWrote 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/instructions/streamlit/streamlit/specs)<a href="https://agentmods.dev/instructions/streamlit/streamlit/specs"><img src="https://agentmods.dev/badge/instructions/streamlit/streamlit/specs/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/instructions/streamlit/streamlit/specs"><img src="https://agentmods.dev/badge/instructions/streamlit/streamlit/specs.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.03922 | $0.03922 |
| Opus 5.5 | $0.01569 | $0.01569 |
| Sonnet 5.5 | $0.00784 | $0.00784 |
| Haiku 4.5 | $0.00392 | $0.00392 |
Grade A, and why
streamlit specs.instructions.md 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 2mo 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 specs — 4 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.
How it starts
The opening of the file, as written. The whole thing — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Streamlit Specs Guide
This directory contains product and tech specs for Streamlit features.
Key files:
YYYY-MM-DD-template/product-spec.md— Template for product specsYYYY-MM-DD-template/tech-spec.md— Template for tech specsREADME.md— Full process documentation
When to Write a Spec
Product spec — focuses on what and why: user-facing problem, proposed API, design mockups, and behavior. Write one when:
- Proposing a new user-facing feature or significant API change
- The what and why need alignment before implementation begins
- Design mockups or UX decisions need sign-off
Tech spec — focuses on how: internal architecture, proto changes, frontend/backend design, state management, and alternatives considered. Write one when:
- The feature is non-user-facing but architecturally significant
- The how needs alignment before implementation (e.g., proto design, state management)
- Multiple implementation paths exist with meaningful trade-offs to document
Does not require a spec:
- Bug fixes, DevOps improvements, small non-controversial enhancements
A single spec directory can contain both a product-spec.md and a tech-spec.md if the
feature warrants both. The directory can also include other assets relevant to the spec
(e.g., design mockups, diagrams, supporting documents).
Creating a Spec
- Copy
specs/YYYY-MM-DD-template/→specs/YYYY-MM-DD-feature-name/ - Fill in
product-spec.mdand/ortech-spec.mdfollowing the template - Create PR titled
[spec] Feature name(keep in Draft until ready for review)
Spec Guidelines
Problem First, Solution Second
Never start with what you want to build. Start with why:
- Link GitHub issues
- Show concrete user pain points and current workarounds
- Include use cases
Present Options, Not Edicts
For non-trivial APIs, show 2-3 options with tradeoffs:
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.
- 2mo ago First seen · 461 lines · 3,922 tokens per session scan A fbcce5b98f89
streamlit specs.instructions.md is an instructions file published in the GitHub repository streamlit/streamlit (46,171 stars, last pushed today), licensed Apache-2.0. It adds 3,922 tokens to every session, about $0.0157 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to specs, differing in 4 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.