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-baselinegit 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-baseline)<a href="https://agentmods.dev/skills/asamassekou10/ship-safe/ship-safe-baseline"><img src="https://agentmods.dev/badge/skills/asamassekou10/ship-safe/ship-safe-baseline/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-baseline"><img src="https://agentmods.dev/badge/skills/asamassekou10/ship-safe/ship-safe-baseline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 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 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 31 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 36 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 44 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 58 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.00043 | $0.00577 |
| Opus 5.5 | $0.00017 | $0.00231 |
| Sonnet 5.5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
ship-safe-baseline 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Safe — Baseline Management
You are helping the user manage their security baseline. A baseline lets teams "accept" current findings as known technical debt and only see new regressions on future scans.
Understand the request
- No flags or just a path → Create/update the baseline
--diff→ Show what changed since the baseline was created--clear→ Remove the baseline
Step 1: Run the baseline command
npx ship-safe@latest baseline $ARGUMENTS 2>&1
If $ARGUMENTS is empty, default to .:
npx ship-safe@latest baseline . 2>&1
For diff mode:
npx ship-safe@latest baseline . --diff 2>&1
For clearing:
npx ship-safe@latest baseline --clear 2>&1
Step 2: Explain the result
If creating a baseline:
- Report how many findings were baselined
- Explain that
.ship-safe/baseline.jsonwas created - Tell the user they can now run
npx ship-safe audit . --baseline(or/ship-safe --baseline) to only see new findings - Recommend adding
.ship-safe/baseline.jsonto version control so the whole team shares the same baseline
If showing diff:
- Report new findings (not in baseline) — these are regressions
- Report resolved findings (in baseline but no longer detected) — these are improvements
- If no changes, confirm the codebase matches the baseline
If clearing:
Confirm the baseline was removed. Future scans will show all findings again.
Step 3: Suggest workflow
After creating a baseline, suggest this workflow:
- CI pipeline: Add
npx ship-safe audit . --baseline --jsonto fail builds only on new findings - Periodic review: Run
/ship-safe-baseline --diffto track progress on reducing technical debt - After fixing: Run
/ship-safe-baseline .to update the baseline
Important Notes
- The baseline uses content-based fingerprints (
rule:path:snippet), not line numbers — so the baseline survives code reformatting and line shifts - Creating a baseline does NOT mean the findings are safe — it means the team acknowledges them and will address them over time
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.
- 1mo ago First seen · 66 lines · 43 tokens per session scan A e486711373e6
ship-safe-baseline is a skill published in the GitHub repository asamassekou10/ship-safe (862 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 577 once invoked, about $0.0002 per session on Opus 5.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.
cred-omega
CISO operacional enterprise para gestao total de credenciais e segredos.
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.
penthera
Offline cyber security agent for the user's own apps and AI coding tools, run locally with the Penthera CLI; open R&D, measured in public. Sets it up in one command ("set up penthera in this repo"). Scans the user's own live URL and repo (TLS, headers, auth, OpenAPI, secrets incl. AI keys, opt-in injection); checks…
skillpm
Install, list, update, scaffold, publish, and sync npm-distributed Agent Skills with skillpm. Use when managing skill dependencies, packaging skills for npm, or refreshing agent directories after dependency or local skill changes.