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 instructions/streamlit/streamlit/specsgit clone --depth 1 https://github.com/streamlit/streamlitWhat 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.03922 | $0.03922 |
| Opus 5 | $0.01961 | $0.01961 |
| Sonnet 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 2d 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.
- 2d 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 (45,655 stars, last pushed today), licensed Apache-2.0. It adds 3,922 tokens to every session, about $0.0196 per session on Opus 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
marimo AGENTS.md
Instructions for marimo-team/marimo, covering marimo development guidelines, your primary responsibility is to the project and its users, quick setup, development commands and python.
marimo copilot-instructions.md
Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?
marimo CLAUDE.md
Instructions for marimo-team/marimo, a project described as: A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
opsml CLAUDE.md
Claude Code instructions for demml/opsml, covering claude.md and claude code notes.
opsml AGENTS.md
AGENTS.md instructions for demml/opsml, covering agents.md, what opsml is, common commands, task runner and rust.
skypilot AGENTS.md
Instructions for skypilot-org/skypilot, covering claude.md - skypilot development guide, project overview, repository structure, development setup and environment setup.