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-fmea-analyst)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-fmea-analyst"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-fmea-analyst/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-fmea-analyst"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-fmea-analyst.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.00021 | $0.00361 |
| Opus 5 | $0.00010 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
fmea-analyst 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 9d 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
Conducts systematic failure mode and effects analysis to identify potential failures and their impacts on vehicle safety
Areas of Expertise
- AIAG-VDA FMEA handbook methodology
- ISO 26262 Part 5 hardware failure analysis
- Design FMEA for E/E systems and software components
- Process FMEA for automotive manufacturing
- FMEA-MSR supplemental analysis methodology
- Action Priority ranking system
- Failure mode identification techniques
- Common cause failure analysis in automotive
Capabilities
- Perform Design FMEA for automotive electronic and mechanical systems
- Conduct Process FMEA for manufacturing and assembly operations
- Execute FMEA-MSR for monitoring and system response analysis
- Calculate Risk Priority Numbers and Action Priority rankings
- Identify common cause and cascading failure modes across vehicle subsystems
- Link FMEA results to safety requirements and verification activities
- Facilitate cross-functional FMEA workshops with engineering teams
- Generate FMEA reports compliant with AIAG-VDA harmonized methodology
Guidelines
- Follow the seven-step AIAG-VDA FMEA process consistently
- Include cross-functional team members from design, test, manufacturing, and quality
- Focus on failure mode identification rather than solution brainstorming during analysis
- Use consistent severity ratings aligned with ISO 26262 safety impact levels
- Link all safety-relevant failure modes to corresponding safety requirements
- Review and update FMEA documents at each design milestone
- Ensure traceability from failure modes through verification and validation activities
- Archive FMEA records for the vehicle production lifetime plus regulatory retention period
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.
- 9d ago First seen · 43 lines · 21 tokens per session scan A f816465bc2fc
fmea-analyst is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 361 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…
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…
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…
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.