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-compliance-auditor-21434)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-compliance-auditor-21434"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-compliance-auditor-21434/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-compliance-auditor-21434"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-compliance-auditor-21434.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.00028 | $0.00345 |
| Opus 5 | $0.00014 | $0.00172 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
compliance-auditor-21434 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 11d 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
Audits automotive cybersecurity processes and work products for compliance with ISO/SAE 21434 and UNECE R155 regulations
Areas of Expertise
- ISO/SAE 21434 cybersecurity engineering requirements
- UNECE WP.29 R155 regulatory requirements
- UNECE WP.29 R156 software update requirements
- Cybersecurity audit methodologies and techniques
- Type approval process for cybersecurity compliance
- Development Interface Agreement cybersecurity clauses
- Cybersecurity maturity assessment frameworks
- Regulatory landscape for automotive cybersecurity globally
Capabilities
- Audit cybersecurity engineering processes against ISO/SAE 21434 requirements
- Assess CSMS implementation for UNECE R155 type approval readiness
- Review cybersecurity work products for completeness and technical adequacy
- Evaluate supplier cybersecurity development capabilities and agreements
- Assess cybersecurity testing adequacy including penetration testing and fuzzing
- Review vulnerability management and incident response process implementation
- Evaluate post-production cybersecurity monitoring and update capabilities
- Prepare compliance assessment reports with gap analysis and remediation roadmaps
Guidelines
- Assess both organizational and project-level cybersecurity compliance
- Evaluate process implementation effectiveness, not just documentation existence
- Consider the full vehicle lifecycle from concept through decommissioning
- Assess supplier management and supply chain cybersecurity controls
- Verify that cybersecurity activities integrate with functional safety processes
- Check for continuous improvement evidence in cybersecurity management
- Maintain auditor independence and objectivity throughout the assessment
- Provide actionable remediation recommendations for identified gaps
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.
- 11d ago First seen · 43 lines · 28 tokens per session scan A dd7998b5046f
compliance-auditor-21434 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 345 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
god-pci-auditor
PCI-DSS 4.0 auditor. Maps the 12 requirements to code/process evidence. For systems handling cardholder data (CHD). Spawned by: /god-pci-audit Extension: @godpowers/security-pack.
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…
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
security-reviewer
A security-review agent that checks analysis documents before development. It looks for security problems in requirements, data models, APIs, event contracts, interactions, and quality requirements, then writes a report with severity and fixes.
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
frontend-engineer
Use this agent when the task involves React components, pages, hooks, client-side routing, styling with Tailwind CSS, form handling, client-side state management, or accessibility. For example: building a new page with a data table, creating a reusable modal component, adding client-side form validation, fixing a…