Versioned security assessment

Report ID: SA-7EFA7426

4/14/2026, 8:43:45 AM

agent-tools security assessment v1

Skill Security Certification Report

Audit History
Audit model: claude Historical report
Skill name
agent-tools
Version
v1
Maintainer
tool-belt
Source
github.com/tool-belt/skills/tree/main/tools/agent-tools/
Coverage
5 Files scanned · 596 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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 analyzer reported 203 potential issues and a risk score of 100/100, but all findings are false positives. The skill consists entirely of markdown documentation files (SKILL.md and four reference files) containing CLI usage examples. The static scanner incorrectly treated markdown code block backticks as Ruby/shell execution, documentation URLs as suspicious network activity, and standard API key environment variable references as secret access. No executable code is present. The only inherent risk is the standard curl-pipe-sh installation pattern for the inference.sh CLI, which is the official installer method and includes checksum verification. The skill contains no prompt injection attempts, no data exfiltration patterns, and no malicious intent.

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 · 596 Lines analyzed

5 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 30 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

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 144 evidence locations

Capability review items (5)
Medium
SKILL.md:16references/authentication.md:6references/authentication.md:44references/cli-reference.md:6
Curl Pipe to Shell Installation Pattern
The skill documentation includes the installation command curl -fsSL https://cli.inference.sh | sh which pipes remote script output directly to the shell. This is the official installer method for the inference.sh CLI and includes checksum verification with SHA-256 and optional Sigstore signature verification. However, this pattern carries inherent risk if the download endpoint were ever compromised. Users are offered a manual install alternative that downloads and verifies the binary separately.
Pattern confirmed in documentation at multiple locations. This is the official installer with checksum verification, but the curl-pipe-sh pattern inherently trusts the delivery endpoint.
Low
SKILL.md:15-101references/app-discovery.md:5-105references/authentication.md:5-53references/cli-reference.md:5-95references/running-apps.md:5-163
Shell Command Examples in Markdown Documentation
Static analyzer flagged 146 instances of shell command patterns across all documentation files. These are markdown code block examples showing CLI usage for the inference.sh platform. The backtick characters are markdown formatting for code blocks, not executable Ruby/shell backtick execution. All commands use the infsh CLI for legitimate AI service operations such as listing apps, running models, and checking task status. No user-controlled input is present in any command example.
All 146 flagged locations are within markdown code blocks containing CLI documentation examples. No executable code exists in these files.
Low
SKILL.md:7-144references/app-discovery.md:110-112references/authentication.md:6-59references/cli-reference.md:6-104references/running-apps.md:152-171
Documentation URLs to Official Platform Endpoints
Static analyzer flagged 32 hardcoded URLs across documentation files. All URLs point to official inference.sh domains (inference.sh, cli.inference.sh, dist.inference.sh, cloud.inference.sh). These are legitimate service endpoints, documentation links, and image references for the platform this skill wraps. No URLs point to external or untrusted domains.
All URLs verified as official inference.sh platform domains. Documentation URLs are expected for a CLI wrapper skill.
Low
references/authentication.md:30references/authentication.md:53references/cli-reference.md:72
API Key Environment Variable Documentation
Static analyzer flagged 3 references to INFSH_API_KEY environment variable. This is the standard API authentication method for the inference.sh platform, documented for CI/CD and scripting use cases. The variable name follows conventional API key naming patterns and is not a leaked credential. No actual key values are present in the files.
INFSH_API_KEY is a documented environment variable name for platform authentication. No actual secret values are present.
Low
references/cli-reference.md:84references/running-apps.md:41SKILL.md:31
Filesystem Path References in Documentation
Static analyzer flagged 5 filesystem path references. These include shell completion file installation paths (e.g., ~/.config/fish/completions/infsh.fish) and local file upload examples (e.g., ~/Pictures/photo.jpg, ../data/video.mp4). All paths are standard documentation examples for CLI usage, not unauthorized file access. The path traversal pattern ../data/video.mp4 is a documented relative path example, not an exploitation attempt.
All paths are documented CLI usage examples for shell completions and local file uploads. No unauthorized file access patterns detected.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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: claude

Analysis state: Complete

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

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