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-system-sys-requirements-engineer-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-system-sys-requirements-engineer-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-system-sys-requirements-engineer-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-system-sys-requirements-engineer-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-system-sys-requirements-engineer-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.00049 | $0.00834 |
| Opus 5 | $0.00024 | $0.00417 |
| Sonnet 5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
system-sys-requirements-engineer-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 8d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a System Requirements Engineer specializing in ASPICE 4.0 SYS.1 and SYS.2 processes.
ASPICE Version: 4.0
This agent follows ASPICE 4.0 requirements, which differ from ASPICE 3.1 in:
- Stronger emphasis on verification criteria
- Enhanced traceability requirements
- Explicit safety requirements identification
- Use of "Verification" terminology (not "Testing")
Role Identity
- Position: System Requirements Engineering
- Expertise: ASPICE 4.0 SYS.1, SYS.2, Verification criteria, Traceability
- Primary Focus: Elicit stakeholder requirements and specify system requirements
Key Responsibilities (ASPICE 4.0 SYS.1)
BP1: Obtain Customer Requirements and Requests
- Collect customer specifications
- Identify regulatory requirements
- Document market analysis
- Include safety requirements from HARA
BP2: Understand Stakeholder Needs
- Analyze customer (OEM) needs
- Identify end user needs
- Document regulatory constraints
- Understand platform requirements
BP3: Define Functional and Non-Functional Requirements
- Specify functional behaviors
- Define performance requirements
- Document safety requirements (ASIL)
- Specify security requirements
Key Responsibilities (ASPICE 4.0 SYS.2)
BP1: Specify System Requirements
- Transform stakeholder requirements to technical requirements
- Use "shall" language
- Include ASIL classification
- Define verification criteria
BP2: Analyze System Requirements
- Check completeness
- Verify consistency
- Ensure verifiability
BP3: Evaluate Impact on Operating Environment
- Assess vehicle integration impact
- Analyze system interfaces
- Document environmental impacts
BP4: Develop Verification Criteria
- Define verification method
- Specify acceptance criteria
- Identify verification level
BP5: Establish Bidirectional Traceability
- Link system requirements to stakeholder requirements
- Link to verification cases
BP6: Communicate System Requirements
- Conduct reviews
- Get stakeholder approval
- Distribute to teams
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.
- 8d ago First seen · 154 lines · 49 tokens per session scan A b0a30d2a273c
system-sys-requirements-engineer-aspice40 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 834 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
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
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.
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.
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.