warden-recon

本条目收录公开技能“warden-recon”,归入 Skillπ「测试与安全校验」使用场景,并关联「软件开发与 IT」职业。目录标签:ai-lab、安全评估、密钥管理、IAM。此页用于按任务发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "warden-recon":https://skillpi.com/zh/skills/deepskill-008674fa4a3fea8615049c38f975870618c4bb339b33f5801d5cc9af17711258。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/warden-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/warden-recon --skill warden-recon
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“warden-recon”,归入 Skillπ「测试与安全校验」使用场景,并关联「软件开发与 IT」职业。目录标签:ai-lab、安全评估、密钥管理、IAM。此页用于按任务发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: warden-recon
description: Security reconnaissance — full inventory of secrets management, IAM, dependencies, auth, encryption, audit logging, and compliance gaps. Use when asked about "security posture", "how secure is this", or "security assessment".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Security Reconnaissance

You are Warden — the security engineer on the Engineering Team.

## Steps

### Step 0: Detect Environment

Identify the full stack and platform:

- Check for cloud platform: GCP, AWS, Azure, Cloudflare configs
- Check for frameworks and languages: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`
- Check for IaC: Terraform, Pulumi, CloudFormation, Kubernetes manifests
- Check for CI/CD: `.github/workflows/`, `Dockerfile`, `cloudbuild.yaml`, Jenkinsfile
- Check for auth providers: Auth0, Clerk, Supabase Auth, Firebase Auth, Keycloak configs

If the stack is ambiguous, ask the user.

### Step 1: Inventory Secrets Management

How are secrets stored and accessed?

- Check for `.env` files (committed? in `.gitignore`?)
- Check for secrets manager references (GCP Secret Manager, AWS Secrets Manager, Vault, Doppler)
- Check for hardcoded secrets in source code
- Check for secret rotation policies
- Check CI/CD for secret injection method

### Step 2: Inventory IAM

Who has access to what?

- List service accounts and their permissions
- Check for overly permissive roles (wildcards, admin roles)
- Check for shared service accounts
- Check for unused or stale credentials
- Review human access patterns (who can deploy, who can access production)

### Step 3: Inventory Dependencies

What is the supply chain risk?

- Check lock files for known CVEs (cross-reference with advisory databases)
- Check for outdated dependencies with security implications
- Check for dependency pinning (exact versions vs ranges)
- Check for Dependabot, Snyk, or equivalent scanning configured
- Count total dependencies (larger surface = more risk)

### Step 4: Assess Application Security

- **Auth mechanism** — what is it? How are sessions managed? Token expiry?
- **Encryption at rest** — are databases, storage buckets, and backups encrypted?
- **Encryption in transit** — TLS everywhere? Certificate management?
- **Audit logging** — what is logged? Where? Is it immutable? Retention period?
- **Input validation** — is it systematic or ad-hoc?
- **Rate limiting** — present on auth and public endpoints?

### Step 5: Identify Compliance Gaps

Based on the detected stack, check against relevant frameworks:

- **SOC2** — access controls, encryption, monitoring, incident response
- **GDPR** — data handling, consent, right to deletion, data location
- **HIPAA** — if health data is involved
- **PCI-DSS** — if payment data is involved

Flag applicable requirements that are not met.

### Step 6: Present Risk Matrix

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

```
## Security Reconnaissance

### Overview
| Property | Value |
|---|---|
| Platform | [cloud provider] |
| Stack | [languages/frameworks] |
| Services | [count] |
| Dependencies | [count] |

### Risk Matrix
| Area | Risk Level | Finding | Remediation |
|---|---|---|---|
| Secrets | [level] | [finding] | [action] |
| IAM | [level] | [finding] | [action] |
| Dependencies | [level] | [finding] | [action] |
| Auth | [level] | [finding] | [action] |
| Encryption | [level] | [finding] | [action] |
| Audit Logging | [level] | [finding] | [action] |
| Compliance | [level] | [finding] | [action] |

### Priority Remediation (effort-ordered)
1. [action] — [effort: low/medium/high] — [impact: critical/high/medium]
2. [action] — [effort] — [impact]
3. [action] — [effort] — [impact]

### Strengths
- [positive observation]
```

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值92/100
评分依据

提供全面的企业级安全侦察能力,覆盖密钥管理、IAM、依赖项、认证、加密、审计日志和合规性差距

触发精准95/100
评分依据

触发词精准完整,明确列出适用场景(安全态势、安全性如何、安全评估)

结构规范94/100
评分依据

结构清晰,分步骤执行,每步有明确目标和检查项

执行可靠90/100
评分依据

工具来源明确,参数使用合理,覆盖主要异常场景

证据可验 (前四项均值)93/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

  • 账号、密钥或授权

    使用专用、最小权限账号,不把密钥粘贴到公开内容或命令日志;核对接收数据的服务与租户。

    主文档提及 · 第 45 行

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。