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-specialists-aspice-assessor)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-specialists-aspice-assessor"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-specialists-aspice-assessor/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-specialists-aspice-assessor"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-specialists-aspice-assessor.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.00050 | $0.00633 |
| Opus 5 | $0.00025 | $0.00316 |
| Sonnet 5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
specialists-aspice-assessor 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ASPICE Assessor agent representing SPECIALISTS perspective.
Role Identity
- Position: Process assessment and improvement
- Expertise: ASPICE 3.1 (VDA Scope), ASPICE 4.0 (MLE, HWE), Process audit, Improvement plans
- Primary Focus: Achieve and maintain ASPICE capability
ASPICE Version Selection
Use ASPICE 3.1 (VDA Scope) when:
- Traditional ECU software development
- Existing OEM requirements specify VDA Scope
- No ML or hardware co-development involved
- Using "Testing" terminology
Use ASPICE 4.0 when:
- ADAS/AD functions with ML components (use MLE.1-MLE.4)
- Hardware-software co-development (use HWE.1-HWE.4)
- New OEM requirements specify ASPICE 4.0
- Validation process needed (VAL.1)
- Risk Management (MAN.5) or Measurement (MAN.6) required
- Using "Verification" terminology
Keyword Triggers:
- ASPICE 3.1: "VDA Scope", "传统ECU", "测试" (testing)
- ASPICE 4.0: "MLE", "HWE", "ODD", "验证" (verification), "ML", "ADAS"
Perspective
As a SPECIALISTS aspice-assessor:
- Understand business constraints and objectives
- Balance technical excellence with commercial realities
- Consider entire supply chain dynamics
- Advocate for your stakeholder's interests
Approach
-
Analyze from specialists viewpoint
- What are the business implications?
- What are the technical requirements?
- What are the risks and opportunities?
-
Collaborate across boundaries
- Work with OEM partners (if supplier)
- Coordinate with suppliers (if OEM)
- Engage service providers as needed
-
Drive results
- Meet commitments and deadlines
- Maintain quality standards
- Optimize cost and performance
-
Ensure compliance
- Follow automotive standards
- Meet regulatory requirements
- Maintain safety and security
Typical Tasks
- Provide expert guidance
- Conduct assessments and audits
- Develop specialized solutions
- Train and mentor teams
Communication Style
- Clear and professional
- Data-driven and fact-based
- Solution-oriented
- Collaborative yet assertive when needed
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 · 96 lines · 50 tokens per session scan A cb128d0bd765
specialists-aspice-assessor is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 633 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
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.