Versioned security assessment

Report ID: SA-35A4B639

6/30/2026, 1:07:27 PM

billing-automation security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
billing-automation
Version
v2
Maintainer
sickn33
Source
github.com/sickn33/antigravity-awesome-skills/tree/main/skills/billing-automation
Coverage
2 Files scanned · 588 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

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.

The static external command and weak cryptography findings are false positives caused by Markdown code fences and billing terms such as amount, payment, and HTML table markup. Human review found no malicious intent or prompt injection, but the playbook includes payment processor calls and unescaped invoice HTML examples that require a marketplace warning.

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

2 Files scanned · 588 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.

Not recorded by this audit

Network access

May connect to external services.

Observed in 2 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Not recorded by this audit

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
resources/implementation-playbook.md:176-188SKILL.md:37-38
Payment Processor Call in Example Code
The playbook demonstrates a Stripe charge call that would contact a payment processor and charge a saved customer if copied into a live environment. This matches the billing purpose and is not malicious, but it can cause financial harm without sandbox controls.
The sample directly calls a payment processor charge API, and the skill warns not to charge real customers in testing. The risk is contextual rather than malicious because billing automation legitimately needs payment integrations.
RISK-002 Medium
resources/implementation-playbook.md:430-461
Unescaped Invoice HTML Template
The invoice HTML example formats customer name, address, and line item content directly into an HTML template. If copied without escaping, customer-controlled billing fields could create HTML injection or stored cross-site scripting in rendered invoices.
The template inserts customer and line item values into HTML without showing escaping or sanitization. The example omits surrounding application context, so the exact exploitability depends on the implementation.
Needs review findings (1)
REVIEW-001 Low
resources/implementation-playbook.md:253-257
Placeholder Billing URL
The playbook includes a hardcoded example.com billing URL inside a dunning email template. It is a documentation placeholder, but implementers should replace it with a configured application URL.
The URL is clearly an example domain and does not indicate exfiltration. It still represents a network-facing billing link that must be configured safely in real deployments.

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 (3)
Low
resources/implementation-playbook.md:16-19resources/implementation-playbook.md:36-52resources/implementation-playbook.md:56-112resources/implementation-playbook.md:116-191resources/implementation-playbook.md:195-264resources/implementation-playbook.md:268-314resources/implementation-playbook.md:318-383resources/implementation-playbook.md:387-462resources/implementation-playbook.md:466-515SKILL.md:33SKILL.md:42
Markdown Code Fences Misclassified as Shell Execution
The reported Ruby or shell backtick execution locations are Markdown code fences or inline file references. They do not execute commands and no shell invocation syntax was found in the reviewed skill files.
The matched backticks delimit Markdown examples and filenames, not executable Ruby or shell expressions. The files are documentation and contain no runnable script entry point.
Low
SKILL.md:3resources/implementation-playbook.md:156resources/implementation-playbook.md:165resources/implementation-playbook.md:400-403resources/implementation-playbook.md:442
Weak Cryptography Findings Are Billing Text False Positives
The weak cryptography alerts occur on billing words and HTML table content, not on MD5, SHA1, DES, or other weak cryptographic algorithms. No evidence of cryptographic implementation was found in the reviewed files.
The cited lines contain invoice descriptions, amount fields, and HTML table markup. None of the cited lines implement or recommend a cryptographic algorithm.
Low
resources/implementation-playbook.md:69-70resources/implementation-playbook.md:390-392
System Reconnaissance Findings Are Identifier False Positives
The system reconnaissance alerts appear on generated billing identifiers such as subscription and invoice IDs. They are ordinary domain model fields and do not collect hostnames, usernames, environment details, or operating system data.
The cited identifiers are billing object IDs, not host or system discovery commands. No evidence of reconnaissance behavior appears near those lines.

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