Vision-Agents: Agent for Claude Code

.claude/agents/repo-workflow-guide.md

repo-workflow-guide is an agent for Claude Code from GetStream/Vision-Agents. It costs 0 tokens per session (820 once invoked), scanned A, original, Apache-2.0.

An agent that reads development rules stored in a repository's docs/ai directory and explains how they apply. It covers coding style, project structure, testing, deployment, and workflow.

In plain words
What is it for?
Consulting project-specific instructions before development work or when the correct coding and delivery process is unclear.
Why use it?
It helps an agent follow local repository conventions instead of guessing how the project should be changed.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is GetStream/Vision-Agents's own configuration. It tells Claude Code how to work on Vision-Agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Vision-Agents configures →

About the project

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.

GetStream/Vision-Agents · 8,193 stars · on GitHub · visionagents.ai

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/GetStream/Vision-Agents/main/.claude/agents/repo-workflow-guide.md
Clone the repo
git clone --depth 1 https://github.com/GetStream/Vision-Agents

Made for: Claude Code.

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

agentmods badge for repo-workflow-guide

README.md
[![agentmods](https://agentmods.dev/badge/agents/getstream/vision-agents/repo-workflow-guide/github.svg)](https://agentmods.dev/agents/getstream/vision-agents/repo-workflow-guide)
Your own site
<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.

agentmods 80×15 button for repo-workflow-guide

Your own site · 80×15
<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>
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 820 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.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

Measured 2mo ago against content hash f90a493d1793, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/agents/repo-workflow-guide.md · 48 lines

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:

  1. 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
  2. Interpret Context: Understand the specific task or question being asked and identify which guidelines are most relevant to address it.

  3. 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
  4. 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
  5. 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.

  6. Prioritize Accuracy: Always base your guidance on the actual content of the documentation. Do not invent or assume guidelines that aren't explicitly documented.

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

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. 2mo ago First seen · 48 lines · 0 tokens per session scan A f90a493d1793

Subscribe to this mod's changes

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.