application-security-review

Reviews application repositories for trust-boundary, auth, validation, and dependency security issues.

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill application-security-review-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: application-security-review
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/software-development/application-security-review
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill application-security-review-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually auditing an application repository for security flaws is slow and easy to get wrong, especially for AI-integrated apps where prompt injection, credential-injecting proxies, and trust-boundary drift create non-obvious exploit paths. This Skill performs a structured source-level security review and produces an operator-facing report with severity, file/line evidence, exploit paths, and fixes. ## Core Features & Use Cases - Trust-boundary-first review: Traces untrusted input into LLM prompts, filesystem/terminal tools, code execution, and document mutations, with dedicated checklists for Electron apps, Office add-ins, local AI agents, and self-hosted agent control planes. - Specialized audit patterns: Detects type drift across trust boundaries, inconsistent URL validation, prototype-pollution-sensitive dictionary lookups, stale-dist test imports, and dev-only vs runtime npm advisory disposition. - Privacy and release verdicts: Scans source and git metadata for PII, secrets, and machine identifiers, then issues separate privacy/secrets and public-release readiness verdicts. - Use Case: Point it at an Electron app that proxies to a local AI agent before shipping; it flags wildcard CORS on the credential-injecting loopback proxy, weak schema validation on model-generated actions, and unpinned dependency advisories, each with path:line evidence and a practical fix. ## Quick Start Ask the agent to review this repository for security issues and produce a severity-ranked report with file and line evidence.

Frequently Asked Questions about application-security-review

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

FAQPage Schema
How do I audit a repository for security issues before release?

Run a source-level security review that reads the README and manifests first, traces untrusted input to powerful sinks like LLM prompts and code execution, then audits dependencies. The review ends with severity-ranked findings, file/line evidence, and a deployment posture verdict.

How to check an AI-integrated app for prompt injection risks?

Treat document, spreadsheet, and page content as untrusted prompt input and trace whether model output can reach tools or side effects. Require strict schema validation on model-driven actions and verify the backend is a restricted profile rather than a full tool-enabled agent.

Does this security review work for Electron desktop apps?

Yes, it includes dedicated checklists for Electron packaging and release readiness, covering entitlements, signing, notarization, SBOM scope, packaged smoke tests, and IPC trust boundaries between renderer and main process.

Can a security review scan git history for leaked secrets and PII?

Yes, public-release reviews scan tracked source, commit metadata, all reachable branches and tags, and fresh remote clones for emails, hostnames, user paths, private org names, and token patterns. Ignored files and stale refs are excluded from the publication verdict.

How are dev dependency vulnerabilities handled in the audit?

Runtime and dev-toolchain risk are separated: npm audit --omit=dev answers the production question while a full audit covers the toolchain. Dev-only advisories are labeled as a release disposition, not equated with live remote exploit paths.

What are the limitations of an automated source security review?

The review favors confirmed issues over speculative ones and labels lower-confidence items as defense-in-depth notes. In strict read-only mode it reports only static conclusions and marks runtime or packaging verification as not executed.