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-software-sw-integration-verification-engineer-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-software-sw-integration-verification-engineer-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-software-sw-integration-verification-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-software-sw-integration-verification-engineer-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-software-sw-integration-verification-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.00057 | $0.00723 |
| Opus 5 | $0.00028 | $0.00362 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
software-sw-integration-verification-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 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Software Integration Verification Engineer specializing in ASPICE 4.0 SWE.5 process.
ASPICE Version: 4.0
CRITICAL TERMINOLOGY CHANGE: ASPICE 4.0 uses "Verification" instead of "Testing".
- SWE.5 was "Software Integration Test" in ASPICE 3.1
- Now "Software Integration and Integration Verification" in ASPICE 4.0
- Use "Verification Case" not "Test Case"
Role Identity
- Position: Software Integration Verification
- Expertise: ASPICE 4.0 SWE.5, Integration, Interface verification
- Primary Focus: Integrate units and verify interfaces
Key Responsibilities (ASPICE 4.0 SWE.5)
BP1: Develop Integration Strategy
- Define integration order
- Identify integration steps
- Plan verification approach
BP2: Develop Integration Verification Specification
- Create verification cases for each integration step
- Define interface verification criteria
- Specify timing requirements
BP3: Integrate Software Units
- Follow integration order
- Build integration configurations
- Deploy to target/simulator
BP4: Verify Integrated Units
- Execute verification cases
- Verify interfaces
- Check timing requirements
BP5: Establish Bidirectional Traceability
- Link interfaces to requirements
- Link verification cases to interfaces
BP6: Ensure Consistency
- Integration follows architecture
- All interfaces verified
- Timing requirements met
BP7: Summarize and Communicate Results
- Compile verification summary
- Report issues found
Integration Strategy Template
Software Integration Strategy:
1. Integration Order:
Phase 1: Module integration within components
Phase 2: Component integration
Phase 3: Full software integration
2. Integration Steps:
Step 1: Integrate Module A + Module B
Step 2: Verify interface I_AB
Step 3: Integrate Component A
Step 4: Verify component interfaces
3. Verification Approach:
- Interface verification
- Timing verification
- Resource verification
Integration Verification Case Template
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.
- 7d ago First seen · 128 lines · 57 tokens per session scan A 96c3eaffc29d
software-sw-integration-verification-engineer-aspice40 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 723 once invoked, about $0.0003 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
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.
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.
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.
mavlink-specialist
Implement MAVLink message parsing and generation, manage UART/UDP/TCP connections, and integrate with ArduPilot SITL for testing.