Aura CLI: The Agentic Developer Shield for Security, Wellness, and Sustainability

I built Aura, an Agentic Developer Shield that transforms the terminal into a proactive partner for security, wellness, and sustainability. As a student, I noticed that while we have great AI tools, they are often passive—you have to ask them for help.

Aura changes that. It proactively:

• 🛡️ Protects (Check): Automatically detects leaked secrets and provides AI remediation.
• 🔥 Sustains (Pulse): Tracks coding rhythms to suggest wellness breaks when "Aura" is fading.
• 🌿 Optimizes (Eco): Audits code for carbon efficiency and algorithmic complexity ($O(n)$).
• 🚀 Launches (Fly): Automates project onboarding through an agentic, interactive setup.
• 📖 Documents (Story): Turns messy Git diffs into professional Founder Journals.
To me, Aura is about Balance. It’s a tool that cares as much about the developer’s health and the planet's carbon footprint as it does about the code itself.

Demo
GitHub Repository:
Key Features in Action:
• Global Command: Aura is fully integrated into the system path. I can run aura pulse _from any directory to check my flow state.
• Interactive Onboarding: The fly module uses pty.spawn to allow real-time interaction during automated project setups.
• Sustainability Reports: Every _aura eco run appends to a persistent GREEN_AUDIT.md, tracking my progress as a green developer.

My Experience with GitHub Copilot CLI
Building Aura would have been impossible in this timeframe without the GitHub Copilot CLI. I used the CLI as a "reasoning engine" rather than just a code generator.
The Impact:

1. Agentic Workflows: I integrated the CLI via subprocesses to act as an "Oracle" for the eco and story modules. It didn't just write code; it analyzed my existing code's logic.
2. Context Awareness: Using the GitHub MCP Server through the CLI allowed Aura to understand when a file wasn't committed to Git, allowing it to suggest simpler security fixes (like .gitignore) rather than complex history rewrites.
3. Stability: The CLI provided a robust, pre-authenticated bridge to LLMs, allowing me to focus on building a beautiful UI with the Rich library instead of worrying about API keys and prompt engineering. GitHub Copilot CLI transformed my development experience from "writing a script" to "architecting an agent."

P.S. I’m a student and still learning the ropes of professional software architecture. If you're an experienced developer and spot any "rookie" mistakes or areas for optimization in my code, I’d love to hear your feedback in the comments! I’m here to learn and grow.