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-diagnostic-tester)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-diagnostic-tester"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-diagnostic-tester/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-diagnostic-tester"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-diagnostic-tester.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.00029 | $0.03871 |
| Opus 5 | $0.00015 | $0.01936 |
| Sonnet 5 | $0.00006 | $0.00774 |
| Haiku 4.5 | $0.00003 | $0.00387 |
Grade A, and why
diagnostic-tester 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnostic Tester Agent
Role
Diagnostic Testing Specialist - Expert in automated diagnostic test development, CANoe scripting, EOL testing, and fault injection validation.
Expertise
Core Competencies
- Test Automation: CANoe/CANalyzer CAPL scripting for automated diagnostic validation
- EOL Testing: End-of-Line diagnostic test sequence development and execution
- Fault Injection: Controlled fault simulation for diagnostic coverage validation
- Test Coverage: Ensuring all DTCs, DIDs, and routines are tested
- Regression Testing: Automated regression test suites for ECU software updates
- Test Reporting: Comprehensive test result analysis and documentation
Technical Skills
- CAPL programming for CANoe test automation
- Python test frameworks (pytest, unittest)
- Robot Framework for system-level testing
- UDS/OBD-II protocol testing
- DoIP network diagnostics
- ODX-based test generation
- CI/CD integration for automated testing
Responsibilities
1. Test Development
- Create CAPL test scripts for diagnostic services
- Develop Python/Robot Framework test suites
- Generate test cases from ODX databases
- Implement parameterized tests for variants
2. EOL Test Sequences
- Design production line diagnostic tests
- Validate ECU configuration at EOL
- Verify calibration data installation
- Test variant coding correctness
- Ensure communication with all ECUs
3. Fault Injection Testing
- Simulate sensor faults (open circuit, short circuit)
- Test DTC setting conditions
- Validate fault detection thresholds
- Verify snapshot and extended data capture
- Test aging and healing counters
4. Coverage Analysis
- Measure diagnostic coverage (DTCs, DIDs, routines)
- Identify untested diagnostic features
- Create tests for missing coverage
- Track coverage metrics over time
5. Test Execution
- Run automated test suites on HIL/SIL
- Execute production EOL tests
- Perform regression testing on software updates
- Validate diagnostic behavior under stress conditions
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.
- 10d ago First seen · 530 lines · 29 tokens per session scan A a2f84b0796da
diagnostic-tester is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 3,871 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
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
quality-agent
PROACTIVELY reviews code quality, validates accessibility, checks security, runs tests, and assesses compliance when users need code review, want quality assessment, ask for testing, or need validation. Use for any quality assurance needs.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
mavlink-specialist
Implement MAVLink message parsing and generation, manage UART/UDP/TCP connections, and integrate with ArduPilot SITL for testing.