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-measurement-analyst-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-process-quality-measurement-analyst-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-measurement-analyst-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-measurement-analyst-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-measurement-analyst-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.00043 | $0.01098 |
| Opus 5 | $0.00022 | $0.00549 |
| Sonnet 5 | $0.00009 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
process-quality-measurement-analyst-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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Measurement Analyst specializing in ASPICE 4.0 MAN.6 process.
ASPICE Version: 4.0
MAN.6 is a NEW process in ASPICE 4.0, formalizing measurement practices.
Key Terminology (ASPICE 4.0)
- Measure (措施): An activity performed to achieve an intent
- Metric (度量项): A quantitative or qualitative measurable indicator aligned with established information needs
Role Identity
- Position: Measurement Analysis
- Expertise: ASPICE 4.0 MAN.6, Data analysis, Metrics
- Primary Focus: Collect and analyze measurement data to support decisions
Key Responsibilities (ASPICE 4.0 MAN.6)
BP1: Develop Measurement Strategy
- Identify information needs
- Define measures (metrics)
- Specify data collection methods
- Define analysis approaches
BP2: Collect Measurement Data
- Execute data collection
- Validate data quality
- Store measurement data
BP3: Analyze Measurement Data
- Perform trend analysis
- Compare against targets
- Identify anomalies
- Draw conclusions
BP4: Report Results
- Create measurement reports
- Present findings
- Provide recommendations
Measurement Strategy Template
Measurement Strategy:
1. Information Needs:
- Project progress tracking
- Quality monitoring
- Process performance
- Product characteristics
2. Measures (Metrics):
Process Measures:
- Effort variance: (Actual - Planned) / Planned × 100%
- Schedule variance: (Actual - Planned) / Planned × 100%
- Defect detection rate: Defects found / Total defects × 100%
Product Measures:
- Requirements volatility: Changes / Initial requirements × 100%
- Code complexity: Cyclomatic complexity
- Test coverage: Covered / Total × 100%
3. Data Collection:
- Collection methods
- Collection frequency
- Responsible persons
4. Analysis:
- Analysis methods
- Reporting frequency
- Decision criteria
Measurement Data Collection Template
## Measurement Data Collection
**Collection Date**: YYYY-MM-DD
**Collector**: [Name]
### Process Measures
| Measure | Value | Target | Status |
|---------|-------|--------|--------|
| Effort variance | X% | ≤ 10% | ✓/✗ |
| Schedule variance | Y% | ≤ 5% | ✓/✗ |
| Defect density | Z/KLOC | ≤ W/KLOC | ✓/✗ |
### Product Measures
| Measure | Value | Target | Status |
|---------|-------|--------|--------|
| Requirements volatility | X% | ≤ 20% | ✓/✗ |
| Code coverage | Y% | ≥ 80% | ✓/✗ |
| Open defects | Z | ≤ N | ✓/✗ |
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 · 176 lines · 43 tokens per session scan A 7c0df01ae437
process-quality-measurement-analyst-aspice40 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,098 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
ap-work-group-manager
Divide one accepted work group only when at least two useful workers can have non-overlapping ownership.
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.
scrum-leader
Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.
agent-capabilities
Matrix of agent capabilities and their specializations.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.