Run any Skill in Manus with one click

apiiro-guardian

Stars0

Forks1

UpdatedApril 26, 2026 at 11:02

Apiiro CLI commands for querying the Guardian AI agent: ask security questions, get analysis and insights about a repository, and manage repository detection. Use this skill whenever the user wants AI-powered security analysis, security posture review, or wants to ask questions about their codebase's security. Also trigger when they need deep analysis of authentication flows, attack surfaces, or want an AI to explain security concepts. Even without mentioning "apiiro" or "guardian", trigger when the user asks things like "is this code secure?", "what's the attack surface here?", or "explain this vulnerability". For dedicated STRIDE threat modeling of a design or feature spec, use the apiiro-threat-model skill instead. For fixing a known risk, use apiiro-fix.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

apiiro

apiiro/marketplace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

name

apiiro-guardian

description

Apiiro Guardian

Ask security questions and get AI-powered analysis about your repository.

Query

Auto-detects the current git repository for context (like risks does). No need to specify a repo explicitly — Guardian picks it up from the git remote.

Important: Before running a query, consider whether the question is repo-specific or org-wide:

Repo-specific (default): questions about the current repo's code, risks, auth flows, dependencies, etc.
Org-wide (--global): questions about the org's policies, top risks across all repos, general security posture, or anything not tied to a specific codebase.

If the question is clearly about the org as a whole (e.g. "top risks last week", "what are our policies"), use --global. If it's unclear, ask the user: "Should I scope this to the current repo, or across your whole org?"

apiiro guardian query "what risks exist in this repo"
apiiro guardian query "deep analysis of auth flow" --model normal
apiiro guardian query "what is STRIDE?" --global          # General security question
apiiro guardian query "top risks across the org last week" --global
apiiro guardian query "what are our org security policies?" --global
apiiro guardian query "detailed analysis" --timeout 120   # 120s timeout
apiiro guardian query "risk analysis" -f analysis.md

Options: --model <fast|normal> (default: fast), -g, --global, --timeout <seconds> (default: 60), -f, --file <path>.

In TTY mode, responses stream with markdown rendering.

Repository Management

apiiro guardian repository detect          # Detect and verify repo in Apiiro
apiiro guardian repository clear           # Clear cached repo info
apiiro guardian repository clear --global  # Clear all cached repos

Detection results are cached for 24 hours.

More from this repository

same repository

apiiro-setup

apiiro/marketplace

Install Apiiro CLI, authenticate, verify version, check available features, and configure hooks

2026-06-090

apiiro-diff-scan

apiiro/marketplace

Apiiro CLI command for comparing two git references for security risks — the primary CI/CD integration point. Use this skill whenever the user mentions diff scanning, comparing branches or commits for security issues, CI/CD security gates, blocking PRs on risk, or wants to wire Apiiro into a build pipeline. Even if the user doesn't say "apiiro", trigger when they say things like "scan this PR", "compare main to my branch for security", "block merges on critical risks", or want to set up security gating in CI. For local secrets/OSS scanning, use apiiro-fast-scan instead.

2026-05-140

apiiro-secure-prompt

apiiro/marketplace

Apiiro CLI command for enhancing developer prompts with security considerations before coding begins. Takes a coding task description and returns the same task with security requirements injected — preserving the original business intent while adding security guardrails. Use this skill whenever the user wants to improve a coding task with security guidance, add security requirements to a task before starting implementation, or get a security-enhanced version of a prompt. Trigger on phrases like "make this prompt more secure", "add security to my task", "what security should I consider for this feature", or when the user is about to start a coding task and wants security baked in. This is different from threat-model (which produces a full STRIDE analysis report) — secure-prompt enhances a *task description* the user is about to implement.

2026-04-290

apiiro-fast-scan

apiiro/marketplace

Apiiro CLI command for quick local security scanning: fast-scan for secrets and OSS vulnerabilities, plus pre-commit hooks. Use this skill whenever the user mentions scanning code locally, secrets detection, OSS vulnerabilities, pre-commit hooks, or wants to check files for security issues before committing. Even if the user doesn't say "apiiro", trigger when they say things like "scan for secrets", "check my code before I push", "are there any leaked credentials", "check dependencies for vulnerabilities", or want to set up local security scanning. For comparing git references in CI/CD, use apiiro-diff-scan instead.

2026-04-260

apiiro-fix

apiiro/marketplace

Apiiro CLI commands for remediating and fixing security risks: get remediation prompts and use Guardian AI to fix findings. Use this skill whenever the user wants to fix, remediate, patch, or resolve a security risk or vulnerability in their repository. Also trigger when they ask "how do I fix this risk", "remediate this finding", "resolve this vulnerability", or want actionable guidance on resolving a security issue. For listing or inspecting risks, use the apiiro-risks skill instead.

2026-04-260

apiiro-risks

apiiro/marketplace

Apiiro CLI commands for viewing and inspecting risks in a repository: list, filter, and get details on known risks. Use this skill whenever the user asks about security risks, vulnerabilities, or findings in their repository. Also trigger when they want to list, filter, or investigate risks by category or severity. Even without mentioning "apiiro", trigger when the user asks things like "what risks does this repo have", "any vulnerabilities here?", "show me the security findings", or "what's the risk level of this project". For fixing or remediating risks, use the apiiro-fix skill instead.

2026-04-260

name

apiiro-guardian

description

Apiiro Guardian

Ask security questions and get AI-powered analysis about your repository.

Query

Auto-detects the current git repository for context (like risks does). No need to specify a repo explicitly — Guardian picks it up from the git remote.

Important: Before running a query, consider whether the question is repo-specific or org-wide:

Repo-specific (default): questions about the current repo's code, risks, auth flows, dependencies, etc.
Org-wide (--global): questions about the org's policies, top risks across all repos, general security posture, or anything not tied to a specific codebase.

apiiro guardian query "what risks exist in this repo"
apiiro guardian query "deep analysis of auth flow" --model normal
apiiro guardian query "what is STRIDE?" --global          # General security question
apiiro guardian query "top risks across the org last week" --global
apiiro guardian query "what are our org security policies?" --global
apiiro guardian query "detailed analysis" --timeout 120   # 120s timeout
apiiro guardian query "risk analysis" -f analysis.md

Options: --model <fast|normal> (default: fast), -g, --global, --timeout <seconds> (default: 60), -f, --file <path>.

In TTY mode, responses stream with markdown rendering.

Repository Management

apiiro guardian repository detect          # Detect and verify repo in Apiiro
apiiro guardian repository clear           # Clear cached repo info
apiiro guardian repository clear --global  # Clear all cached repos

Detection results are cached for 24 hours.