viipers-audit

Audits and hardens a multi-agent AI trading terminal built on Next.js, Drizzle ORM, and Postgres.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/jasonviipers/vipers --skill viipers-audit-jasonviipers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: viipers-audit
Source: https://github.com/jasonviipers/vipers/tree/main/.agents/skills/audit
Command: npx skills add https://github.com/jasonviipers/vipers --skill viipers-audit-jasonviipers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Automated trading systems fail in expensive, non-obvious ways: mock data leaking into production paths, AI output trusted without validation, race conditions doubling exposure, duplicate order submissions, and risk gates that can be bypassed. Generic code review instincts miss these domain-specific failure modes, so working on the Viipers multi-agent trading terminal requires a structured audit methodology and enforced safety invariants. ## Core Features & Use Cases - Full production-readiness audits: Builds and maintains a living checklist at docs/TRADING_SYSTEM_AUDIT.md covering agents, risk engine, database concurrency, exchange integration, security, and testing, with evidence-based marking conventions. - Risk-gate invariant enforcement: Ensures AI agents can only propose trades while a deterministic risk engine approves them and only the order-executor agent reaches the broker, flagging any bypass path as critical. - Narrow task support: Applies the same core principles (idempotency, LLM output validation, fail-loud error handling) to smaller changes like adding an agent, fixing a duplicate-order bug, or reviewing a PR. - Use Case: When asked to make the Viipers repo production-ready, the skill guides a stage-by-stage trace of the consensus pipeline (sentiment, analysis, coordination, risk, execution), hunts for hidden mocks and race conditions, and closes out with an executive summary of verified and unverifiable items. ## Quick Start Ask the AI to run a full production-readiness audit of the Viipers trading terminal and create the audit checklist document.

Frequently Asked Questions about viipers-audit

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

FAQPage Schema
How do I audit an AI trading system for production readiness?

Start by tracing the full pipeline from signal to execution, then work a checklist covering mock data on production paths, database concurrency, exchange integration, secrets handling, and error handling. Mark items complete only with concrete evidence and flag anything requiring live credentials as unverifiable.

How do I prevent AI agents from bypassing risk checks in automated trading?

Enforce a mandatory deterministic risk gate between agent proposals and execution, where only a single order-executor component has broker access and only acts on risk-approved proposals. Any code path letting an agent reach the broker directly should be treated as a critical finding.

How do I prevent duplicate order submissions in a trading system?

Use an idempotency key on order submission so retries, double-clicks, or duplicate agent runs become no-ops instead of duplicate orders. Also protect balance reads and writes with real database transactions or row locks rather than read-modify-write in application code.

Can this audit approach be used for trading systems other than Viipers?

Yes, the methodology applies to general automated-trading-system audits even when Viipers is not named, since the same architecture and safety invariants apply. The checklist template should be adapted to whatever components the actual code contains.

What are the limitations of auditing without production credentials?

Live exchange connectivity, production database concurrency behavior, and deployed infrastructure cannot be verified without real credentials and traffic. These items should be explicitly marked as unverifiable with notes on what would be needed, never reported as passing.