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-service-discovery-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-service-discovery-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-service-discovery-engineer/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-service-discovery-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-service-discovery-engineer.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.00020 | $0.00341 |
| Opus 5 | $0.00010 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
service-discovery-engineer 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 7d 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
Designs and implements service discovery mechanisms enabling dynamic service availability management in vehicle architectures
Areas of Expertise
- SOME/IP-SD protocol internals and configuration
- Multicast group management for service discovery
- Service lifecycle management in automotive systems
- Discovery timing optimization for vehicle startup
- Service dependency graph analysis and resolution
- DDS discovery protocols for automotive applications
- mDNS and DNS-SD for vehicle service discovery
- Service registry patterns for centralized discovery
Capabilities
- Implement SOME/IP-SD for dynamic service registration and subscription
- Design service discovery strategies for startup, runtime, and recovery scenarios
- Configure multicast and unicast discovery parameters for network efficiency
- Implement service availability monitoring and notification mechanisms
- Design graceful service degradation when required services are unavailable
- Optimize discovery timing for fast service availability after vehicle startup
- Implement service versioning and compatibility checking in discovery flows
- Debug service discovery issues in complex multi-ECU vehicle networks
Guidelines
- Minimize service discovery time to support fast vehicle startup requirements
- Design for robustness against arbitrary ECU startup and shutdown ordering
- Implement appropriate timeouts and retry strategies for discovery operations
- Limit multicast discovery traffic to prevent network congestion at startup
- Handle service version mismatches gracefully with clear error reporting
- Test discovery behavior under network segmentation and recovery scenarios
- Document service discovery configuration parameters and their impact
- Monitor discovery protocol overhead to ensure it stays within budget
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.
- 7d ago First seen · 43 lines · 20 tokens per session scan A 5bd32f185d05
service-discovery-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 341 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-09-03.
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…
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
Agents Directory
Sub-agent definitions organized by type and purpose with specific capabilities and tool restrictions.
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
ha-esphome-config-reviewer
Produces one bundled, read-only device-level review of an ESPHome device configuration: config-pattern conformance, credential and API/OTA hardening, schema currency against the official ESPHome docs, Home-Assistant-driven binding correctness, display rendering discipline, display design conformance (palette roles…