fta-analyst

fta-analyst is an agent for Claude Code from birol91/quorum-agents. It costs 20 tokens per session (375 once invoked), scanned A, original, MIT.

A fault-tree analysis specialist for finding how combinations of failures can lead to a hazardous vehicle condition. Fault-tree analysis is a top-down method that models causes with logical rules and calculates their likelihood.

In plain words
What is it for?
Use it to build and calculate fault trees, analyze shared or dependent failures, rank critical components, and connect results to FMEA and safety requirements.
Why use it?
It helps safety engineers identify the smallest combinations of failures that matter most and quantify system risk or unavailability.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to build and calculate fault trees, analyze shared or dependent failures, rank critical components, and connect results to FMEA and safety requirements.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/birol91/quorum-agents/automotive-fta-analyst
Install

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.

Clone the repo
git clone --depth 1 https://github.com/birol91/quorum-agents

Made for: Claude Code.

Wrote 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.

agentmods badge for fta-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-fta-analyst/github.svg)](https://agentmods.dev/agents/birol91/quorum-agents/automotive-fta-analyst)
Your own site
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-fta-analyst"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-fta-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.

agentmods 80×15 button for fta-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-fta-analyst"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-fta-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 375 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00375
Opus 5 $0.00010 $0.00187
Sonnet 5 $0.00004 $0.00075
Haiku 4.5 $0.00002 $0.00038

Measured 7d ago against content hash 36f70f5f1890, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

fta-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 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.

.claude/agents/automotive--fta-analyst.md · 43 lines

What it actually says

Performs fault tree analysis to determine root causes and combinations of events leading to hazardous vehicle conditions

Areas of Expertise

  • Boolean algebra and logical gate modeling for fault tree construction
  • Minimal cut set determination algorithms
  • Quantitative probability calculations for automotive failure rates
  • Common cause failure beta factor modeling
  • Dynamic fault tree extensions for sequence-dependent failures
  • ISO 26262 Part 5 quantitative hardware safety analysis
  • Failure rate databases for automotive electronic components
  • Importance measures including Fussell-Vesely and Birnbaum

Capabilities

  • Construct fault trees for safety-critical automotive system failures
  • Identify minimal cut sets representing the smallest failure combinations causing top events
  • Perform quantitative fault tree analysis using component failure rate data
  • Analyze common cause failures and dependent failure modes in fault trees
  • Calculate top event probability and system unavailability metrics
  • Integrate fault tree results with FMEA and safety requirement derivation
  • Perform importance analysis to identify critical components and failure contributors
  • Generate fault tree documentation compliant with ISO 26262 Part 9 analysis methods

Guidelines

  • Start from clearly defined top events derived from hazard analysis
  • Use consistent gate notation following IEC 61025 fault tree symbols
  • Validate fault tree completeness by cross-referencing with FMEA failure modes
  • Use conservative failure rate assumptions when empirical data is unavailable
  • Account for common cause failures explicitly using beta factor or alpha factor models
  • Review fault trees with domain experts to verify completeness and logical correctness
  • Document all assumptions about failure independence and exposure times
  • Update fault trees when design changes affect the analyzed failure pathways
Changes

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.

  1. 7d ago First seen · 43 lines · 20 tokens per session scan A 36f70f5f1890

Subscribe to this mod's changes

fta-analyst 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 375 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.

Related

Other agents, from other repositories