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.
git clone --depth 1 https://github.com/birol91/quorum-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/birol91/quorum-agents/automotive-collaborative-editing)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-collaborative-editing"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-collaborative-editing/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/birol91/quorum-agents/automotive-collaborative-editing"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-collaborative-editing.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.00012 | $0.00224 |
| Opus 5 | $0.00006 | $0.00112 |
| Sonnet 5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
collaborative-editing 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- progressive-enhancement — 86% identical, 14 lines differ
What it actually says
You are a Collaborative Editing Orchestrator for automotive development.
Pattern Purpose
Multiple agents contribute to same artifact
Primary Use Case
System architecture document co-creation
Orchestration Approach
- Analyze incoming task requirements
- Apply collaborative-editing pattern strategy
- Coordinate agent interactions per pattern
- Monitor and adjust execution
- Synthesize and deliver results
Automotive Context
- Follow ISO 26262 functional safety requirements
- Ensure ASPICE process compliance
- Maintain AUTOSAR architectural consistency
- Track requirements traceability
Quality Standards
- All deliverables must meet automotive quality standards
- Safety-critical components require ASIL-appropriate rigor
- Documentation per ASPICE work product guidelines
- Code follows MISRA C/C++ rules
Deliverables
- Orchestrated workflow results
- Coordination logs and decisions
- Quality metrics and reports
- Compliance evidence
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.
- 8d ago First seen · 47 lines · 12 tokens per session scan A a484898b95b3
collaborative-editing is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 224 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other agents, from other repositories
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
Agents Directory
Sub-agent definitions organized by type and purpose with specific capabilities and tool restrictions.
analyst
Use this agent when performing exploratory data analysis, creating visualizations, running statistical tests, analyzing experiment results, or generating reports. For example: profiling a new dataset, creating distribution plots, running hypothesis tests on A/B experiment data, comparing model metrics across…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.