security-audit

Run Bandit, pip-audit, and detect-secrets scans for vulnerabilities and credential leaks.

Updated May 2, 2026
One-click install
npx skills add https://github.com/gmanch94/agora --skill security-audit-gmanch94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/gmanch94/agora/tree/main/.claude/skills/security-audit
Command: npx skills add https://github.com/gmanch94/agora --skill security-audit-gmanch94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bandit, pip-audit, detect-secrets, sys, subprocess, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents security regressions by running a broad, milestone-ready audit that detects hardcoded secrets, dependency vulnerabilities, and risky code patterns before changes reach real ILL/tenant infrastructure.

Core Features & Use Cases

  • Multi-surface scanning for real risks: Executes Bandit for security-sensitive Python code, pip-audit for locked dependency CVEs, and detect-secrets to catch newly introduced credential patterns.
  • Agora-specific leakage detection: Explicitly checks for credential exposure paths such as saga-event payload and outbox payload content that could end up in audit logs or database rows.
  • Operationally timed for safe review: Use it when auth/credentials code changes, before opening Agora to a real ReShare tenant, and periodically every ~10 PRs.

Example: After modifying ReShare or NCIP client credential handling, run this audit before merging to ensure no secrets were introduced in saga/outbox data and no vulnerable transitive dependencies were added.

Quick Start

Run the bundled scanner from the repo root using the project venv so it executes Bandit, pip-audit, and detect-secrets consistently against your current codebase.

Frequently Asked Questions about security-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect hardcoded secrets and dependency vulnerabilities before a release?

Detect secrets and vulnerabilities by running a comprehensive security audit using Bandit, pip-audit, and detect-secrets. This scans your Python code and locked dependencies to flag high or critical severity risks and credential leaks before changes reach production.

How does detect-secrets scan for credential exposure in saga-event payloads?

Detect-secrets scans saga-event payload and outbox payload content to identify agora-specific credential exposure paths. It evaluates these surfaces to ensure newly introduced secret patterns do not end up persisting in database rows or audit logs.

What's the best way to run Bandit and pip-audit consistently against a Python codebase?

Run the bundled scanner from your repository root using the project virtual environment. This executes Bandit and pip-audit consistently against your current codebase to evaluate security-sensitive code and locked dependency CVEs.

When should I run a dependency audit and secrets detection in my workflow?

Run a dependency audit and secrets detection during milestone readiness, after modifying auth or credentials modules, before real tenant exposure, and periodically every 10 pull requests to prevent security regressions.

Can I use pip-audit to check for transitive dependency vulnerabilities?

Yes, pip-audit scans your locked dependencies to find transitive dependency CVEs. It evaluates the results alongside code and secrets scans to ensure no vulnerable packages were added before merging.

Does this security audit check for risky Python code patterns as well as dependency CVEs?

Yes, the security audit executes Bandit to find risky security-sensitive Python code patterns alongside pip-audit for dependency CVEs and detect-secrets for hardcoded credentials, providing multi-surface scanning.