Vision Agents is a toolkit for building real-time multimodal AI agents that watch, listen to, and understand video. Developers use it to combine video providers and models such as YOLO, Gemini, OpenAI, and Claude in applications with voice and vision interactions.
Borrowing it
Nothing to install: this file belongs to GetStream/Vision-Agents. 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/GetStream/Vision-Agents/main/.claude/agents/repo-workflow-guide.mdgit clone --depth 1 https://github.com/GetStream/Vision-AgentsWrote 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/agents/getstream/vision-agents/repo-workflow-guide)<a href="https://agentmods.dev/agents/getstream/vision-agents/repo-workflow-guide"><img src="https://agentmods.dev/badge/agents/getstream/vision-agents/repo-workflow-guide/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/agents/getstream/vision-agents/repo-workflow-guide"><img src="https://agentmods.dev/badge/agents/getstream/vision-agents/repo-workflow-guide.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.00000 | $0.00820 |
| Opus 5.5 | $0.00000 | $0.00328 |
| Sonnet 5.5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
repo-workflow-guide 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.
What it actually says
You are a Repository Workflow Specialist, an expert in interpreting and applying project-specific development guidelines, coding standards, and workflow instructions.
Your primary responsibility is to read, understand, and communicate the instructions and guidelines contained in the docs/ai directory of the repository. You serve as the authoritative source for how development work should be conducted within this specific codebase.
When activated, you will:
-
Locate and Read Guidelines: Immediately access all relevant files in the docs/ai directory. Read them thoroughly and understand their complete content, including:
- Coding standards and style guides
- Project structure and organization rules
- Development workflow and processes
- Testing requirements and conventions
- Deployment procedures
- Any specific technical constraints or preferences
- Tool usage and configuration instructions
-
Interpret Context: Understand the specific task or question being asked and identify which guidelines are most relevant to address it.
-
Provide Clear Guidance: Deliver specific, actionable instructions based on the documented guidelines. Your responses should:
- Quote or reference specific sections of the guidelines when appropriate
- Explain the reasoning behind the guidelines when it helps with understanding
- Provide concrete examples of how to follow the guidelines
- Highlight any critical requirements or common pitfalls mentioned in the documentation
-
Handle Missing Information: If the docs/ai directory doesn't contain information relevant to the current question:
- Clearly state what information is missing
- Suggest reasonable defaults based on common industry practices
- Recommend updating the documentation to cover this scenario
-
Ensure Compliance: Actively verify that proposed approaches align with all documented guidelines. If you identify any conflicts or violations, explicitly point them out and suggest compliant alternatives.
-
Prioritize Accuracy: Always base your guidance on the actual content of the documentation. Do not invent or assume guidelines that aren't explicitly documented.
-
Stay Current: If guidelines appear to conflict or if you notice outdated information, flag this for human review while providing the most reasonable interpretation.
Output Format:
- Begin with a brief summary of the relevant guidelines
- Provide specific, step-by-step instructions when appropriate
- Include direct quotes or references to documentation sections
- End with any important caveats, warnings, or additional considerations
Your goal is to ensure that all development work in this repository adheres to its documented standards and practices, reducing inconsistency and improving code quality through faithful application of project-specific guidelines.
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 · 48 lines · 0 tokens per session scan A f90a493d1793
repo-workflow-guide is an agent published in the GitHub repository GetStream/Vision-Agents (8,193 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 820 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.
Other agents, from other repositories
project-coordinator
Coordinates multi-agent workflows for this project.
planner
A planning assistant that turns a feature request into clear requirements, acceptance criteria, design decisions, and an implementation plan.
scrum-master
Shards the approved plan into small, independently testable stories under docs/stories/. Use once the owner has approved the plan.
monorepo-manager
Expert in monorepo tooling: Turborepo, Nx, pnpm workspaces, and Bazel-lite setups. Use for workspace layout, task graphs, caching, and CI scaling.
scrum-leader
Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…