Skip to content

notque/vexjoy-agent / skills/infrastructure/deploy

deploy

Flagged

Deploy and infrastructure: web deploy, cron, package install, shell configuration.

Security report

Flagged

Static analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.

Commit
871f649901b317d675e63f2dcce2b6515e046230
Content hash
9c351e06c3831f47a89a53f9fad0cb10a63f00b0895ade3f768f0c60db750cc1
Scanned
2026-11-17
Scanner version
skillxone-scan-1.0.0
Policy version
0.1-draft
Decision
2 open critical or high findings.
Verification expires
Not applicable

Findings (2 high, 3 medium, 1 info)

  • highCMD-HISTORY-LOG-WIPEreferences/starting-processes.md:32

    Shell history or system logs are erased, which hides what was done.

    nohup long_running_task > /var/log/task.log 2>&1 &

    Suggested fix: Remove commands that clear history or logs.

    Report as false positive

  • highCMD-HISTORY-LOG-WIPEreferences/starting-processes.md:91

    Shell history or system logs are erased, which hides what was done.

    > /var/log/$(basename "$1").log 2>&1 \

    Suggested fix: Remove commands that clear history or logs.

    Report as false positive

  • The skill sets something to run automatically later (scheduled task, login item or shell start-up file).

    systemctl enable --now fail2ban && fail2ban-client status

    Suggested fix: Do not install persistent jobs or edit shell start-up files. Tell the user what to add if they want it.

    Report as false positive

  • The skill refers to shell history, a location that holds private data or credentials.

    $HISTFILE # Path to history file (default: ~/.zsh_history)

    Suggested fix: Do not read credential stores or private files. If the task needs a credential, ask the user to provide it through the environment.

    Report as false positive

  • mediumFILE-SHELL-HISTORYreferences/zsh-shell-config.md:243

    The skill refers to shell history, a location that holds private data or credentials.

    HISTFILE=~/.zsh_history

    Suggested fix: Do not read credential stores or private files. If the task needs a credential, ask the user to provide it through the environment.

    Report as false positive

  • infoINT-BROAD-ALLOWED-TOOLSSKILL.md:5

    SKILL.md pre-approves unrestricted shell access through `allowed-tools`, so the agent may run commands without asking.

    allowed-tools: - Read - Write - Bash - Grep - Glob - Edit - Agent

    Suggested fix: Restrict the tool, for example `Bash(git status:*)`, or leave approval to the user.

    Report as false positive

Checks run

  • prompt-injection
  • dangerous-commands
  • credentials
  • network
  • file-access
  • integrity

Checks skipped

  • dependencies: No dependency manifest in the skill directory.
  • gitleaks: gitleaks is not installed on this host.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall