openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

[PR #75] [CLOSED] Add AgentGuard — supply chain security scanner for agent skills #247

New Issue
Closed
opened 2026-02-15 17:16:29 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:16:29 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/openclaw/clawhub/pull/75
Author: @rondorkerin
Created: 1/31/2026
Status: ❌ Closed

Base: main ← Head: add-agentguard-security-scanning

📝 Commits (3)

  • 830f847 docs: add security scanning guide with AgentGuard
  • 8f070f1 fix: address PR review comments
  • c112988 fix: update agentguard install to use published npm package agentguard-ai

📊 Changes

1 file changed (+74 additions, -0 deletions)

View changed files

➕ docs/security-scanning.md (+74 -0)

📄 Description

What

Adds a security scanning guide to ClawdHub docs, introducing AgentGuard as a tool for scanning skills before installation or as a CI/CD gate.

Why this matters

Agent skills run with access to filesystems, credentials, and networks. During testing, AgentGuard detected a credential stealer in a published skill — it was reading ~/.ssh/ and ~/.aws/credentials then exfiltrating them via HTTPS. Trust score: 0/100.

As ClawdHub grows, the ecosystem needs a security layer. AgentGuard is that layer — think npm audit for agent skills.

What AgentGuard detects

  • 🔑 Credential exfiltration (SSH keys, AWS creds, API tokens)
  • 💉 Code injection (eval, exec, Function constructor)
  • 📡 Outbound data exfiltration
  • 🎭 Obfuscation (base64/hex-encoded payloads)
  • ⚠️ Compound threats (credential read + network call in same file)

Test results

AgentGuard has been tested against both clean skills and intentionally malicious samples:

  • Clean skills score 90-100 (safe)
  • Known malicious skill scored 0/100 with 3 CRITICAL + 2 HIGH findings
  • Full test suite passes with pattern detection for all major threat categories

Links

Happy to iterate on the docs or discuss integrating AgentGuard into the ClawdHub publish pipeline as a built-in security gate.

Greptile Overview

Greptile Summary

Adds a new documentation page (docs/security-scanning.md) that introduces AgentGuard as an optional pre-install and CI/CD gate scanner for third-party skills, outlining install/scan commands, detection categories, and a trust-score interpretation.

This fits into the existing docs/ set of operational/reference pages (similar frontmatter + “read_when” taxonomy), giving users a concrete workflow for reducing supply-chain risk from skill bundles before running them with filesystem/network access.

Confidence Score: 4/5

  • This PR is safe to merge; it’s a docs-only change with minor wording/clarity nits.
  • Only a single new markdown doc is added; no code paths or runtime behavior change. Findings are limited to consistency/clarity of wording and an ambiguity in the --fail-on example semantics.
  • docs/security-scanning.md

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

Context used:

  • Context from dashboard - AGENTS.md (source)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/openclaw/clawhub/pull/75 **Author:** [@rondorkerin](https://github.com/rondorkerin) **Created:** 1/31/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-agentguard-security-scanning` --- ### 📝 Commits (3) - [`830f847`](https://github.com/openclaw/clawhub/commit/830f847a2cf8add28bc77156c83eaebde6d8c94a) docs: add security scanning guide with AgentGuard - [`8f070f1`](https://github.com/openclaw/clawhub/commit/8f070f1718816b63c5a2cfcdbeed3ca00b339a1d) fix: address PR review comments - [`c112988`](https://github.com/openclaw/clawhub/commit/c112988da9cbfd2ed62b28a2b2ba4e159ef05b65) fix: update agentguard install to use published npm package agentguard-ai ### 📊 Changes **1 file changed** (+74 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/security-scanning.md` (+74 -0) </details> ### 📄 Description ## What Adds a security scanning guide to ClawdHub docs, introducing [AgentGuard](https://github.com/rondorkerin/agentguard) as a tool for scanning skills before installation or as a CI/CD gate. ## Why this matters Agent skills run with access to filesystems, credentials, and networks. During testing, **AgentGuard detected a credential stealer in a published skill** — it was reading `~/.ssh/` and `~/.aws/credentials` then exfiltrating them via HTTPS. Trust score: 0/100. As ClawdHub grows, the ecosystem needs a security layer. AgentGuard is that layer — think `npm audit` for agent skills. ## What AgentGuard detects - 🔑 Credential exfiltration (SSH keys, AWS creds, API tokens) - 💉 Code injection (eval, exec, Function constructor) - 📡 Outbound data exfiltration - 🎭 Obfuscation (base64/hex-encoded payloads) - ⚠️ Compound threats (credential read + network call in same file) ## Test results AgentGuard has been tested against both clean skills and intentionally malicious samples: - Clean skills score 90-100 (safe) - Known malicious skill scored 0/100 with 3 CRITICAL + 2 HIGH findings - Full test suite passes with pattern detection for all major threat categories ## Links - **Repo**: https://github.com/rondorkerin/agentguard - **Install**: `npm install -g agentguard` - **RFC for inter-agent security messaging**: https://github.com/openclaw/openclaw/issues/5517 Happy to iterate on the docs or discuss integrating AgentGuard into the ClawdHub publish pipeline as a built-in security gate. <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Adds a new documentation page (`docs/security-scanning.md`) that introduces AgentGuard as an optional pre-install and CI/CD gate scanner for third-party skills, outlining install/scan commands, detection categories, and a trust-score interpretation. This fits into the existing `docs/` set of operational/reference pages (similar frontmatter + “read_when” taxonomy), giving users a concrete workflow for reducing supply-chain risk from skill bundles before running them with filesystem/network access. <h3>Confidence Score: 4/5</h3> - This PR is safe to merge; it’s a docs-only change with minor wording/clarity nits. - Only a single new markdown doc is added; no code paths or runtime behavior change. Findings are limited to consistency/clarity of wording and an ambiguity in the `--fail-on` example semantics. - docs/security-scanning.md <!-- greptile_other_comments_section --> <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **Context used:** - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=a1d58d20-b4dd-4cbb-973a-9fd7824e1921)) <!-- /greptile_comment --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 17:16:29 -05:00
yindo closed this issue 2026-02-15 17:16:29 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#247
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?