Versioned security assessment

Report ID: SA-C4408032

6/28/2026, 6:29:21 AM

skill-name security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
skill-name
Version
v6
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/_template
Coverage
5 Files scanned · 1,677 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

2 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static analysis found many command, network, secret, filesystem, and script patterns. Most are false positives from security training examples and rule templates, but the CI asset contains a real remote installer piped directly into a shell. No confirmed malicious intent or prompt injection was found, but the unsafe CI pattern and unfinished template quality make this unsuitable for publication without remediation.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

5 Files scanned · 1,677 Lines analyzed

3 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Observed in 1 evidence location

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 1 evidence location

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (2)

RISK-001 High
assets/ci-config-template.yml:240
Remote Installer Piped to Shell
The CI template downloads a third-party installer over the network and executes it directly with a shell. This is a true positive because users copying the template would run unauthenticated remote code in CI unless they replace this pattern with a pinned, verified installation method.
The static pattern is confirmed by semantic context: a CI pipeline step performs network download and immediate shell execution. It is presented as a reusable template, so the supply-chain risk is real even without malicious intent.
RISK-002 Medium
SKILL.md:3-11SKILL.md:13-16SKILL.md:133-151
Unfinished Generic Skill Template
The primary skill file still contains placeholders for name, maintainer, category, patterns, troubleshooting, and examples. This is not a direct exploit, but it increases operational risk because users may copy incomplete security guidance into production workflows.
The placeholder content is directly visible in the skill metadata and body. The risk is content quality and misuse, not hidden malicious behavior.
Needs review findings (1)
REVIEW-001 Medium
assets/ci-config-template.yml:134assets/ci-config-template.yml:164assets/ci-config-template.yml:250assets/ci-config-template.yml:323
Executable CI Template Requires Trust Review
The CI asset is designed to run security scanners, parse reports, read generated files, and post pull request comments. These actions are legitimate for DevSecOps, but they should be reviewed before publication because they combine external commands, filesystem reads, network-based actions, and GitHub token access.
The operations match the stated CI security scanning purpose, but the combined permissions and execution behavior require maintainer review. I did not find evidence that secrets are exfiltrated.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Low
assets/rule-template.yaml:128-165assets/rule-template.yaml:268-299references/EXAMPLE.md:135-162references/EXAMPLE.md:235-279references/WORKFLOW_CHECKLIST.md:177-195
Security Example Snippets Trigger Static Patterns
The hardcoded secrets, weak crypto, XSS, C2, malware, and reconnaissance hits are mostly examples inside security rule or reference documentation. They demonstrate vulnerable and fixed patterns rather than executing those patterns as part of the skill.
The flagged text is in documentation sections that explain vulnerability classes and remediation. I did not find evidence that these examples are executed automatically.
Low
assets/rule-template.yaml:43-45assets/rule-template.yaml:191-193SKILL.md:155-157
Reference Links Are Documentation URLs
Most hardcoded URL findings point to OWASP, CWE, example.com, or security documentation references. These are expected documentation links and do not show data exfiltration.
The URLs are cited as references or placeholders. The only network URL I found with execution impact is reported separately as the high-risk CI installer pattern.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable