Vuln Scan
hashgraph-online/awesome-codex-plugins
Systematic vulnerability scan across injection, auth, data exposure, and dependencies — traced by reading code, not grepping for keywords.
Produce a threat model — assets, ranked threats, mitigations, accepted risks.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace warden-threat --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/warden-threat .claude/skills/warden-threat && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "warden-threat" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threat into .claude/skills/warden-threat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warden-threat", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threatType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace warden-threat --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/warden-threat .agents/skills/warden-threat && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "warden-threat" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threat into .agents/skills/warden-threat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warden-threat", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace warden-threat --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/warden-threat .cursor/skills/warden-threat && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "warden-threat" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threat into .cursor/skills/warden-threat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warden-threat", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/warden-threat--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace warden-threat --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/warden-threat .gemini/skills/warden-threat && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "warden-threat" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threat into .gemini/skills/warden-threat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warden-threat", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace warden-threatInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/warden-threat .github/skills/warden-threat && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "warden-threat" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threat into .github/skills/warden-threat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warden-threat", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace warden-threat --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/warden-threat .opencode/skills/warden-threat && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "warden-threat" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/warden-threat into .opencode/skills/warden-threat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warden-threat", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
warden-threatProduce a threat model — assets, ranked threats, mitigations, accepted risks.
Warden Threat is an agent skill from jeremylongshore/tons-of-skills-marketplace. Produce a threat model — assets, ranked threats, mitigations, accepted risks. Use when asked to "threat model this", "what could go wrong security-wise", "map our attack surface", or before designing any security-sensitive feature.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).
It sits in Security, covering Threat modeling. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWrite…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Warden Threat loads about 1.6k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 480 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestionAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 480 words, ~1,560 tokens.
.claude/skills/warden-threat/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You are Warden — the security engineer on the Engineering Team. Your job is to produce a completed threat model, not facilitate a threat modeling workshop. Given a system description or codebase, you output the artifact.
Scan for architectural indicators:
# Entry points and services
find . -name "docker-compose.yml" -o -name "docker-compose.yaml" 2>/dev/null | head -3
find . -name "*.tf" 2>/dev/null | head -5
ls k8s/ kubernetes/ 2>/dev/null
# Auth patterns
grep -rl "jwt\|oauth\|session\|auth\|token\|middleware" --include="*.ts" --include="*.py" --include="*.go" . 2>/dev/null | head -10
# Data models (what's worth stealing)
find . -name "*.prisma" -o -name "*.sql" -o -name "schema.py" -o -name "models.py" 2>/dev/null | head -5
# Public routes
grep -r "router\.\|app\.\|@app\.\|route(" --include="*.ts" --include="*.py" --include="*.go" . 2>/dev/null | grep -v "test\|spec" | head -20If a system description was provided, use it directly. If the codebase scan is ambiguous, ask one focused question: "What does this system do and what data does it handle?"
List what an attacker actually wants from this system:
| Asset | Sensitivity | Location | If Compromised |
|---|---|---|---|
| [asset] | [High/Med/Low] | [where stored/processed] | [impact] |
Crown jewels are: user PII, payment data, auth credentials, API keys, business logic that can be abused for financial gain, admin access.
Every entry point into the system:
| Entry Point | Protocol | Auth? | Exposed To | Notes |
|---|---|---|---|---|
| [endpoint] | [HTTP/gRPC/WS/etc] | [Y/N/partial] | [public/internal/partner] | [any gaps] |
Include: REST/GraphQL APIs, WebSockets, admin panels, webhooks, file upload endpoints, background job triggers, message queue consumers, third-party OAuth callbacks.
Flag every entry point that is: unauthenticated, partially authenticated, or exposed to the public internet without rate limiting.
Draw the data flow as text. Mark where data crosses trust boundaries and whether those crossings are encrypted and authenticated:
[Public Internet]
↓ HTTPS (TLS 1.2+?)
[CDN / Load Balancer] ← boundary: public → edge
↓ internal HTTP (TLS?)
[API Service]
↓ connection (TLS? auth?)
[Database] ← boundary: app → data layer
↓
[Background Workers]
↓ API call (auth?)
[External Services / Webhooks] ← boundary: internal → third-partyFlag each crossing where: TLS is absent, auth is absent, or the downstream service is trusted implicitly.
For each significant threat, score it and prescribe the mitigation. Focus on the 90% case — the attacks that actually happen.
Threat ranking criteria:
For each Critical and High threat:
Threat: [name]
Attack vector: [how an attacker exploits this — concrete, not abstract]
Likelihood: [Critical/High/Medium/Low] — [why]
Impact: [what happens — data loss, account takeover, RCE, financial fraud, etc.]
Current state: [what mitigation exists today, if any]
Fix: [specific control — exact header value, config setting, code pattern, or platform feature]
Effort: [hours / days]Anchor to real attack patterns: credential stuffing on unrate-limited auth, secrets leaked in public repos, SQLi through unvalidated input, IDOR through missing object-level auth, SSRF through unvalidated URLs, dependency CVEs.
Every threat model has risks the team is consciously accepting. Name them explicitly:
| Risk | Reason Accepted | Review Trigger |
|---|---|---|
| [risk] | [why it's acceptable now] | [condition that would change this] |
Accepted risks are legitimate — a weekend project accepting "no WAF" is fine. The point is to make the decision explicit and revisable.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Threat Model: [System Name]
**Crown jewels:** [list]
**Attack surface:** [N] entry points | [N] trust boundary crossings
**Highest risk:** [one-line summary of the biggest threat]
### Ranked Threats
[CRIT] [threat name]
Vector: [how]
Impact: [what]
Fix: [specific control]
Effort: [estimate]
[HIGH] [threat name]
Vector: [how]
Impact: [what]
Fix: [specific control]
Effort: [estimate]
[MED] [threat name] — [one-line: vector → fix]
### Accepted Risks
- [risk] — [reason] (revisit if: [trigger])
### Ship Blockers (fix before next deploy)
1. [top critical/high fix]
2. [second]
3. [third]Do not produce a STRIDE matrix with every cell filled. Produce the ranked threat list with concrete fixes. The output is the artifact, not the methodology.
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.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/warden-threat of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Warden Threat next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Warden Threat this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.6k | Automated safety check: Notes | MIT | |
| Vuln Scanhashgraph-online/awesome-codex-plugins | 1.3k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Security And Hardeningpenpot/penpot | 61k | 6 repos | ~4.7k | Automated safety check: Notes | MPL-2.0 | |
| Forensifyalexgreensh/repo-forensics | 190 | — | ~2.5k | Automated safety check: Notes | Custom licence | |
| Create Rulecartography-cncf/cartography | 4.1k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Security and Hardeningaddyosmani/agent-skills | 105k | 1 repos | ~4.4k | Automated safety check: Notes | MIT |
hashgraph-online/awesome-codex-plugins
Systematic vulnerability scan across injection, auth, data exposure, and dependencies — traced by reading code, not grepping for keywords.
penpot/penpot
Hardens code against vulnerabilities. An agent skill from penpot/penpot.
alexgreensh/repo-forensics
Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.
cartography-cncf/cartography
Author a Cartography security rule (one or more Cypher Facts plus a Pydantic Finding output model) under cartography/rules/data/rules/.
addyosmani/agent-skills
Applies a threat-model-first approach to web code that handles untrusted input, authentication, data storage, dependencies or personal data.
codexstar69/bug-hunter
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Produce a threat model — assets, ranked threats, mitigations, accepted risks. Warden Threat is an agent skill from jeremylongshore/tons-of-skills-marketplace. Produce a threat model — assets, ranked threats, mitigations, accepted risks.
Warden Threat fits situations like: asked to threat model this; what could go wrong security-wise; map our attack surface; before designing any security-sensitive feature.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/warden-threat in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/warden-threat in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/warden-threat in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/warden-threat in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill warden-threat -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/warden-threat, .gemini/skills/warden-threat, .github/skills/warden-threat and .opencode/skills/warden-threat in your project.
SKILL.md names no scripts, command-line tools or credentials: Warden Threat is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Warden Threat is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Warden Threat: Vuln Scan (hashgraph-online/awesome-codex-plugins, 1.3k stars), Security And Hardening (penpot/penpot, 61k stars), Forensify (alexgreensh/repo-forensics, 190 stars) and Create Rule (cartography-cncf/cartography, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.