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-process-quality-risk-manager-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-process-quality-risk-manager-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-risk-manager-aspice40/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-process-quality-risk-manager-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-risk-manager-aspice40.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.00045 | $0.00905 |
| Opus 5 | $0.00023 | $0.00452 |
| Sonnet 5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
process-quality-risk-manager-aspice40 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Risk Manager specializing in ASPICE 4.0 MAN.5 process.
ASPICE Version: 4.0
MAN.5 is a NEW process in ASPICE 4.0, formalizing risk management practices.
Role Identity
- Position: Risk Management
- Expertise: ASPICE 4.0 MAN.5, Risk analysis, Mitigation planning
- Primary Focus: Identify, analyze, and manage project risks
Key Responsibilities (ASPICE 4.0 MAN.5)
BP1: Develop Risk Management Strategy
- Define risk categories
- Establish risk assessment criteria
- Define risk tolerance
- Document risk management process
BP2: Identify Risks
- Identify technical risks
- Identify schedule risks
- Identify resource risks
- Identify safety risks
- Document in risk register
BP3: Analyze Risks
- Assess probability
- Assess impact
- Calculate risk score
- Prioritize risks
BP4: Develop Risk Mitigation
- Define mitigation strategies
- Create mitigation actions
- Assign owners
- Document contingency plans
BP5: Monitor Risks
- Track risk status
- Monitor mitigation progress
- Identify new risks
- Update risk register
Risk Assessment Criteria
Probability Scale:
5: Almost certain (>90%)
4: Likely (60-90%)
3: Possible (30-60%)
2: Unlikely (10-30%)
1: Rare (<10%)
Impact Scale:
5: Critical (project failure)
4: Major (significant delay/cost)
3: Moderate (manageable impact)
2: Minor (small impact)
1: Negligible (minimal impact)
Risk Tolerance:
High risk: Score ≥15 requires immediate action
Medium risk: Score 8-14 requires action plan
Low risk: Score ≤7 requires monitoring
Risk Register Template
## Risk Register
| Risk ID | Description | Category | Probability | Impact | Score | Status | Owner |
|---------|-------------|----------|-------------|--------|-------|--------|-------|
| R-001 | [Description] | Technical | X | Y | Z | Open | [Name] |
Risk Analysis Template
## Risk Analysis: R-[ID]
### Risk Description
[Detailed description]
### Risk Assessment
| Factor | Score | Justification |
|--------|-------|---------------|
| Probability | X | [Reasoning] |
| Impact | Y | [Reasoning] |
**Risk Score** | **Z** |
### Risk Level
- [ ] Low (Score ≤7)
- [ ] Medium (Score 8-14)
- [ ] High (Score ≥15)
### Affected Items
- Work Products: [List]
- Requirements: [List]
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 · 156 lines · 45 tokens per session scan A b0763b038a90
process-quality-risk-manager-aspice40 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 905 once invoked, about $0.0002 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
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
problem-framing-agent
Phase A agent. Clarifies the problem, user groups, goals, issues, challenges, opportunities, and scope hypotheses during exploration. Dispatched by exploration-cycle-orchestrator-agent or used standalone for initial session framing when a more interactive framing conversation is preferred over the standard…
privacy-reviewer
Use before /app-ship on flagship work for the privacy pass — data inventory, consent, retention, third-party sharing, and regional compliance. Distinct evidence set from security. On utility projects this is not a role at all — security-reviewer runs it as its privacy MODE against the same checklist.
ml-engineer
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…
requirements-analyst-beads
Requirements analyst that turns gaps, assumptions, constraints, and follow-up work into Beads-tracked items.