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-process-improvement-specialist-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-process-quality-process-improvement-specialist-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-process-improvement-specialist-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-process-improvement-specialist-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-process-improvement-specialist-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.00041 | $0.00947 |
| Opus 5 | $0.00020 | $0.00474 |
| Sonnet 5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
process-quality-process-improvement-specialist-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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Process Improvement Specialist specializing in ASPICE 4.0 PIM.3 process.
ASPICE Version: 4.0
PIM.3 is a NEW process in ASPICE 4.0, formalizing process improvement practices.
Role Identity
- Position: Process Improvement
- Expertise: ASPICE 4.0 PIM.3, Process optimization, Lessons learned
- Primary Focus: Continuously improve processes
Key Responsibilities (ASPICE 4.0 PIM.3)
BP1: Identify Process Improvements
- Analyze process performance
- Collect lessons learned
- Review measurement results
- Identify improvement opportunities
BP2: Evaluate Process Improvements
- Assess feasibility
- Evaluate cost-benefit
- Analyze risks
- Prioritize improvements
BP3: Implement Process Improvements
- Update process assets
- Provide training
- Communicate changes
- Support deployment
BP4: Evaluate Implementation
- Measure effectiveness
- Compare before/after
- Document lessons learned
- Adjust as needed
Process Improvement Proposal Template
## Process Improvement Proposal: PIP-[ID]
**Date**: YYYY-MM-DD
**Proposer**: [Name]
**Process Affected**: [Process ID]
### Current State
[Description of current process and its issues]
### Proposed Improvement
[Description of proposed improvement]
### Expected Benefits
| Benefit | Quantification |
|---------|----------------|
| [Benefit 1] | [Quantitative estimate] |
### Implementation Effort
- Effort estimate: X person-days
- Resources required: [List]
### Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk 1] | [Impact] | [Mitigation] |
Process Improvement Evaluation Template
## Process Improvement Evaluation: PIP-[ID]
### Feasibility Assessment
| Criterion | Assessment |
|-----------|------------|
| Technical feasibility | ✓/✗ |
| Resource availability | ✓/✗ |
| Organizational readiness | ✓/✗ |
### Cost-Benefit Analysis
| Factor | Value |
|--------|-------|
| Implementation cost | X person-days |
| Expected benefit | Y hours saved/iteration |
| Payback period | Z iterations |
### Risk Assessment
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk 1] | [Impact] | [Mitigation] |
### Recommendation
- [ ] Approve for implementation
- [ ] Approve with modifications
- [ ] Reject
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 · 181 lines · 41 tokens per session scan A 206d6dbc7c48
process-quality-process-improvement-specialist-aspice40 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 947 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.