Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add asamassekou10/ship-safe --skill ship-safe-red-teamgit clone --depth 1 https://github.com/asamassekou10/ship-safeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/asamassekou10/ship-safe/ship-safe-red-team)<a href="https://agentmods.dev/skills/asamassekou10/ship-safe/ship-safe-red-team"><img src="https://agentmods.dev/badge/skills/asamassekou10/ship-safe/ship-safe-red-team/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/asamassekou10/ship-safe/ship-safe-red-team"><img src="https://agentmods.dev/badge/skills/asamassekou10/ship-safe/ship-safe-red-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 14 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 20 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 26 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 57 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.00738 |
| Opus 5 | $0.00036 | $0.00369 |
| Sonnet 5 | $0.00015 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
ship-safe-red-team scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Safe — Red Team Scan
You are running a multi-agent red team scan using Ship Safe's 29 security agents.
Step 1: Run the red team scan
npx ship-safe@latest red-team $ARGUMENTS --json --no-ai 2>/dev/null
If $ARGUMENTS is empty, default to .:
npx ship-safe@latest red-team . --json --no-ai 2>/dev/null
If the user wants specific agents only, use the --agents flag:
npx ship-safe@latest red-team . --agents injection,auth,ssrf --json --no-ai 2>/dev/null
Available agents include: injection, auth, ssrf, supply-chain, config, llm, mobile, git-history, cicd, api, supabase-rls, mcp, agentic, rag, pii, agent-config, memory-poisoning, managed-agent, hermes, agent-attestation, agentic-supply-chain, roblox-security, model-scan, trust-boundary, slopsquat, clickfix, install-guard
Step 2: Parse and present results
The JSON output contains findings from each agent. Present results grouped by agent:
For each agent that found issues:
- Agent name and category (e.g., "InjectionTester — Code Vulnerabilities")
- Finding count by severity
- Top findings — list critical and high severity findings with:
- File and line number
- Rule name and description
- Code context (if available, show the flagged line with surrounding lines)
- Suggested fix
- Confidence level
Agent summary table
Show a table: Agent | Findings | Critical | High | Medium
Agents with zero findings
List them briefly as clean — this is useful context.
Step 3: Deep dive and remediation
For the most critical findings:
- Read the actual source file for full context
- Explain the vulnerability in plain language — what could an attacker do?
- Offer to fix it with a concrete code change
- After fixing, offer to re-run just that agent to verify:
npx ship-safe@latest red-team . --agents <agent>
Step 4: Recommendations
Based on the results, suggest:
- Which agents to focus on (highest finding count or most critical findings)
- Whether to create a baseline (
/ship-safe-baseline) for the current state - Framework-specific hardening tips based on detected stack (from recon agent)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 72 lines · 73 tokens per session scan A 685488d85c58
ship-safe-red-team is a skill published in the GitHub repository asamassekou10/ship-safe (842 stars, last pushed 4d ago), licensed MIT. It adds 73 tokens to every session and 738 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
security-review
Security audit focused on OWASP Top 10 — injection, auth flaws, secrets exposure, IDOR, and more. Use when reviewing code for vulnerabilities, before deploying to production, or auditing a new codebase.
security-audit
Audit code and infrastructure for security vulnerabilities. Use when performing security reviews, checking for OWASP Top 10 issues, auditing dependencies, or hardening applications.
depsguard
Install and run DepsGuard, a zero-dependency CLI that scans and fixes package manager configs (npm, pnpm, yarn, bun, uv) for supply chain security best practices.
optimize-cc-md
Interactively helps users optimize their CLAUDE.md files. Use when user asks to "optimize my CLAUDE.md", "my CLAUDE.md is too long", "improve organization", or "split my CLAUDE.md". Runs validation, explains issues conversationally, and helps create @import files to reduce size and improve structure.
skillpm
Manage npm-distributed Agent Skill packages with skillpm.
validate-cc-md
Validates CLAUDE.md files for size, imports, and structure. Use when user asks to "check my CLAUDE.md", "why is my CLAUDE.md too long", "validate imports", or "fix CLAUDE.md errors". Checks file size limits (30KB warning, 50KB error), @import directives, frontmatter in .claude/rules/, and section organization.