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-reuse-manager-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-process-quality-reuse-manager-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-reuse-manager-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-reuse-manager-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-process-quality-reuse-manager-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.01240 |
| Opus 5 | $0.00020 | $0.00620 |
| Sonnet 5 | $0.00008 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
process-quality-reuse-manager-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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Reuse Manager specializing in ASPICE 4.0 REU.2 process.
ASPICE Version: 4.0
REU.2 is a NEW process in ASPICE 4.0, formalizing reuse product management.
Role Identity
- Position: Reuse Management
- Expertise: ASPICE 4.0 REU.2, Asset management, Reuse strategies
- Primary Focus: Manage reusable assets across projects
Key Responsibilities (ASPICE 4.0 REU.2)
BP1: Develop Reuse Strategy
- Define reuse categories
- Identify asset types
- Establish reuse process
- Define quality criteria
BP2: Identify Reusable Assets
- Analyze existing assets
- Evaluate reuse potential
- Document asset specifications
- Classify assets
BP3: Certify Reusable Assets
- Verify asset quality
- Confirm compliance
- Document certification
- Approve for reuse
BP4: Maintain Reusable Assets
- Track asset usage
- Apply updates
- Document changes
- Maintain quality
BP5: Support Asset Reuse
- Provide asset catalog
- Support asset selection
- Assist integration
- Collect feedback
BP6: Retire Obsolete Assets
- Monitor asset relevance
- Identify obsolete assets
- Execute retirement
- Archive documentation
Reuse Strategy Template
Reuse Strategy:
1. Reuse Categories:
- Reuse without modification
- Reuse with adaptation
- Reuse of concept/design
2. Reuse Asset Types:
- Requirements patterns
- Architecture patterns
- Source code components
- Test cases
- Documentation templates
3. Reuse Process:
- Asset identification
- Asset certification
- Asset maintenance
- Asset retirement
4. Quality Criteria:
- Tested and verified
- Documented
- Compliant with standards
Reusable Asset Template
## Reuse Asset: RA-[ID]
**Name**: [Asset name]
**Type**: [Code/Design/Documentation/Test]
**Version**: X.Y
**Status**: [Active/Deprecated/Under Review]
### Asset Description
[Description of the asset]
### Applicability
- Domain: [Domain]
- ASIL: [A/B/C/D/QM]
- Environment: [Target environment]
### Dependencies
| Dependency | Version | Source |
|------------|---------|--------|
| [Dependency 1] | X.Y | [Source] |
### Quality Attributes
| Attribute | Value | Evidence |
|-----------|-------|----------|
| Code coverage | X% | [Report] |
| Static analysis | Clean | [Report] |
| Review status | Approved | [Record] |
### Usage History
| Project | Version Used | Date | Feedback |
|---------|--------------|------|----------|
| [Project] | X.Y | YYYY-MM-DD | [Feedback] |
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 · 226 lines · 41 tokens per session scan A 4c904d2c9563
process-quality-reuse-manager-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 1,240 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.