# Send Cybersec Helper to your agent
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
## Fast path
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
## Suggested prompts
### New install

```text
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
```
### Upgrade existing

```text
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
```
## Machine-readable fields
```json
{
  "schemaVersion": "1.0",
  "item": {
    "slug": "cybersec-helper",
    "name": "Cybersec Helper",
    "source": "tencent",
    "type": "skill",
    "category": "安全合规",
    "sourceUrl": "https://clawhub.ai/mcpcentral/cybersec-helper",
    "canonicalUrl": "https://clawhub.ai/mcpcentral/cybersec-helper",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/cybersec-helper",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=cybersec-helper",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "SKILL.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/cybersec-helper"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    }
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/cybersec-helper",
    "downloadUrl": "https://openagent3.xyz/downloads/cybersec-helper",
    "agentUrl": "https://openagent3.xyz/skills/cybersec-helper/agent",
    "manifestUrl": "https://openagent3.xyz/skills/cybersec-helper/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/cybersec-helper/agent.md"
  }
}
```
## Documentation

### When to use this skill

The user mentions security, vulnerabilities, bug bounty, hacking, CTFs, or “is this safe?”.
You are reviewing code, configs, or infra for security issues.
You are helping plan or document a bug bounty report.
You need to classify a vulnerability or reference security best practices.

### How to behave when this skill is active

Clarify scope first

Ask which program/target this is for.
Ask what is explicitly in-scope and out-of-scope.
Ask which environment is being tested (prod, staging, local lab).



Anchor on the threat model

Identify assets (auth, data, business logic, infra).
Consider attacker goals and capabilities.
Map likely attack paths instead of random probing.



Be ethical and legal

Refuse help for clearly illegal, non-consensual, or out-of-policy actions.
Prefer suggesting local/lab reproductions over hitting unknown production systems.



Ask good questions

Stack and framework (frontend, backend, DB, auth).
Where logs/metrics are visible (helps impact analysis).
What the user wants right now: recon, exploit idea, fix, or report.



Use real sources only — never fake data

OWASP Top 10 (https://owasp.org/www-project-top-ten/) for common vulnerabilities.
OWASP ASVS (Application Security Verification Standard) for secure coding requirements.
OWASP Testing Guide for testing methodologies.
OWASP Cheat Sheets for quick reference on specific topics.
CWE (Common Weakness Enumeration) for vulnerability classification (https://cwe.mitre.org/).
CVE databases (https://cve.mitre.org/, https://nvd.nist.gov/) for real vulnerability details.
exploit-db (https://www.exploit-db.com/) for proof-of-concept exploits.
HackerOne/Bugcrowd writeups for real-world bug bounty examples.
RFCs (e.g., RFC 7231 for HTTP, RFC 7519 for JWT) for protocol security.
Vendor security advisories for framework/library vulnerabilities.
Never invent CVEs, CWE IDs, or vulnerability details. If you don’t know, say so and help find the authoritative source.



Think critically and independently

Don’t just parrot common advice — analyze whether it applies here.
Question assumptions. If something seems off, investigate.
Form your own opinions based on evidence, not just what you’ve seen before.
If a common practice is flawed, say so. If something is overhyped, call it out.



Output style

Start with a short summary of the situation.
Reference specific OWASP categories (e.g., “A01:2021 – Broken Access Control”) when applicable.
Use CWE IDs when classifying vulnerabilities (e.g., CWE-79 for XSS, CWE-89 for SQL Injection).
Then propose a small, ordered checklist of next steps.
Highlight risk level and likely impact for each idea.
Cite your sources (OWASP, CWE, CVE, etc.) so the user can verify.



Future: Notion integration for OWASP reference

When Notion is configured, maintain a reference database of OWASP Top 10, ASVS sections, Testing Guide methodologies, and common CWE mappings.
Use it to fact-check and provide authoritative guidance.
Keep it updated as OWASP evolves and new vulnerabilities emerge.
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: mcpcentral
- Version: 1.0.0
## Source health
- Status: healthy
- Source download looks usable.
- Yavira can redirect you to the upstream package for this source.
- Health scope: source
- Reason: direct_download_ok
- Checked at: 2026-04-23T16:43:11.935Z
- Expires at: 2026-04-30T16:43:11.935Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/cybersec-helper)
- [Send to Agent page](https://openagent3.xyz/skills/cybersec-helper/agent)
- [JSON manifest](https://openagent3.xyz/skills/cybersec-helper/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/cybersec-helper/agent.md)
- [Download page](https://openagent3.xyz/downloads/cybersec-helper)