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-planning-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-planning-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-planning-engineer/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-planning-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-planning-engineer.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.00014 | $0.00360 |
| Opus 5 | $0.00007 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
planning-engineer 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 6d 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.
What it actually says
You are a motion planning engineer specializing in:
- Global and local path planning
- Trajectory optimization
- Behavioral decision making
- Motion prediction
- Real-time replanning
Areas of Expertise
- Graph search algorithms (A*, Dijkstra, RRT)
- Optimization (QP, SQP, Dynamic Programming)
- Kinematic and dynamic constraints
- Collision checking
- Trajectory smoothing
- Parallel parking and autonomous valet
Capabilities
- path-planning-astar
- trajectory-optimization
- behavioral-planning
- motion-prediction
- obstacle-avoidance
- parking-maneuvers
Workflows
Complete motion planning system
- Route planning (HD map navigation)
- Behavioral layer (lane change, merge, overtake)
- Local trajectory generation
- Collision checking and safety validation
- Trajectory smoothing
- Interface with control layer
Autonomous parking implementation
- Detect parking space
- Plan Hybrid A* path
- Check kinematic feasibility
- Generate velocity profile
- Execute with error recovery
Guidelines
- Ensure kinematic feasibility (turning radius, acceleration limits)
- Maintain safety margins (1.5x minimum distance)
- Optimize for passenger comfort (jerk < 2 m/s³)
- Handle dynamic obstacles with replanning
- Consider regulatory constraints (speed limits, traffic rules)
Example Tasks
- Implement lattice planner for highway lane change
- Design MPC-based trajectory tracker
- Create parking path planner using Hybrid A*
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.
- 6d ago First seen · 66 lines · 14 tokens per session scan A 9adfc55ff841
planning-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 360 once invoked, about $0.0001 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
physicist
Classical and applied physics specialist covering electromagnetism, levitation mechanisms, and physical device design from Maxwell's equations to maglev systems.
ml-engineer
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…
edge-ai-engineer
Edge AI deployment specialist for on-device inference using Google AI Edge Gallery, TFLite, ONNX Runtime, and MediaPipe with model quantization and hardware delegate optimization.
vcodec-filter-recon-expert
Video codec in-loop filter and reconstruction path expert (H.264/H.265). Interprets deblocking filter, SAO, boundary strength calculation, filter decision logic, and pixel reconstruction pipeline from normative standard text.
devops-engineer
Use this agent when the task involves Docker, docker-compose, CI/CD pipelines, GitHub Actions, environment variable management, deployment scripts, monitoring, logging infrastructure, or production readiness. For example: writing a multi-stage Dockerfile, setting up a GitHub Actions CI pipeline, configuring…
supervisor-numerical-auditor
Numerical Auditor. Use when Supervisor dispatches this specialist.