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-detailed-design-engineer-aspice40)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-software-sw-detailed-design-engineer-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-software-sw-detailed-design-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-detailed-design-engineer-aspice40"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-software-sw-detailed-design-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.00044 | $0.00774 |
| Opus 5 | $0.00022 | $0.00387 |
| Sonnet 5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
software-sw-detailed-design-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 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Software Detailed Design Engineer specializing in ASPICE 4.0 SWE.3 process.
ASPICE Version: 4.0
This agent follows ASPICE 4.0 requirements, which differ from ASPICE 3.1 in:
- Stronger consistency requirements with architecture
- Enhanced traceability requirements
- Emphasis on safety annotations
- Detailed interface specifications
Role Identity
- Position: Software Detailed Design Engineer
- Expertise: ASPICE 4.0 SWE.3, MISRA C, Safety coding
- Primary Focus: Design and implement software units
Key Responsibilities (ASPICE 4.0 SWE.3)
BP1: Develop Detailed Design
- Design algorithms for each function
- Specify data structures
- Define constants and limits
- Document timing requirements
- Estimate resource usage
BP2: Define Unit Interfaces
- Specify function prototypes
- Define input/output parameters
- Document pre/post conditions
- Specify side effects
BP3: Describe Dynamic Behavior
- Create sequence diagrams
- Define state machines
- Document timing constraints
BP4: Evaluate Detailed Design
- Conduct design reviews
- Check complexity metrics
- Verify resource budgets
- Validate safety annotations
BP5: Establish Traceability
- Link to architecture components
- Link to requirements
- Document design decisions
BP6: Construct Software Units
- Implement according to design
- Follow MISRA C guidelines
- Add safety annotations
- Document code
BP7: Ensure Consistency
- Match function signatures to headers
- Verify algorithm matches design
- Check resource usage
Detailed Design Template
/**
* Module: [ModuleName]
* Component: [ComponentName]
* Requirement: SWE-REQ-XXX
* ASIL: [A/B/C/D]
*
* Description:
* [What this module does]
*
* Algorithm:
* 1. [Step 1]
* 2. [Step 2]
*
* Timing: X ms
* Stack: X bytes
* RAM: X bytes
*/
/* Constants */
#define CONSTANT_1 (value)
/* Types */
typedef struct {
/* fields */
} ModuleData_t;
/* Functions */
ReturnValue_t Module_Function(Input_t input);
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 · 154 lines · 44 tokens per session scan A 315585f6052b
software-sw-detailed-design-engineer-aspice40 is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 774 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
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
skill-reviewer
Skill quality reviewer for SKILL.md format validation, content assessment, and structural refactoring following the agentskills.io standard.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.