- Home
- Skills
- Code Quality & Review
- Lazarus Mode — Principal Engineer Rigour
Lazarus Mode — Principal Engineer Rigour
Apply principal-engineer rigour to implementation, architecture, code review, validation and releases.
Free
Works with the AI Agents you already use
About this skill
Guides an engineering agent through requirements, design trade-offs, failure handling, security, performance, meaningful validation and completion checks. Use it when a feature, review or release needs staff/principal-level scrutiny. It follows repository conventions and favours the simplest adequate design.
Requires an agent with access to your project and the tools needed for the requested work; it does not guarantee defect-free output.
Free and open source under the MIT licence. Created by kabudu. Source and local installation instructions: https://github.com/kabudu/engineering-agent-skills
Instruction-based workflow; results depend on the agent, repository context and available tools. It cannot guarantee correctness or replace human judgement. CI, remote review and release verification require access to the relevant systems.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Permissions
Access depends on the requested task. Reads project files; implementation can edit files and run shell commands. Research, hosted PR reviews and releases can use browser/network access and existing authenticated tools. Follow user authorization and repository rules before remote changes. No external account is required for local analysis.