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 agentmods add commands/vibeforge1111/vibeship-plugin/scangit clone --depth 1 https://github.com/vibeforge1111/vibeship-pluginWrote 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/commands/vibeforge1111/vibeship-plugin/scan)<a href="https://agentmods.dev/commands/vibeforge1111/vibeship-plugin/scan"><img src="https://agentmods.dev/badge/commands/vibeforge1111/vibeship-plugin/scan.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00012 | $0.01294 |
| Opus 5 | $0.00006 | $0.00647 |
| Sonnet 5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
scan 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 3d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeship Security Scan
The user wants to scan code for security vulnerabilities. Help them run a comprehensive scan.
Step 1: Determine What to Scan
Ask (if not clear) what they want to scan:
- Current project - Scan the codebase they're working in
- GitHub repository - Scan a specific repo URL
- Specific files - Focus on particular files or directories
Step 2: Start the Scan
Use scanner_scan tool:
scanner_scan({
repo_url: "https://github.com/owner/repo",
branch: "main" // optional
})
For local projects, you'll need to:
- Check if project has a GitHub remote
- Use that URL for scanning
- Or explain that local-only scanning requires pushing to GitHub first
Step 3: Monitor Progress
The scan runs asynchronously. Use scanner_status to check progress:
scanner_status({ scan_id: "..." })
Keep the user informed:
- "Scan started! ID: xxx"
- "Scanning... 45% complete"
- "Scan finished! Found X issues."
Step 4: Present Results
When scan completes, show a clear summary:
## 🔍 Security Scan Results
**Repository**: [repo name]
**Scan ID**: [id]
**Completed**: [timestamp]
### Summary
- 🔴 Critical: X
- 🟠 High: X
- 🟡 Medium: X
- 🟢 Low: X
### Top Issues
1. **[Severity] [Issue Title]**
- File: `path/to/file.js:42`
- CWE: CWE-79 (Cross-Site Scripting)
- Description: [brief explanation]
2. ...
### Next Steps
- Use `/vibeship-scan fix` to get AI-generated fixes
- Use `/vibeship-scan details [finding-id]` to learn more about a specific issue
Step 5: Offer Follow-up Actions
Based on results, offer to:
- Look up CVE/CWE details:
scanner_lookup_cve,scanner_lookup_cwe - Get AI-generated fixes:
scanner_get_fix - Generate master fix prompt:
scanner_master_prompt
Handling Errors
If Scanner MCP isn't connected:
## Scanner Unavailable
**What happened:** Can't connect to the security scanning service.
**You have alternatives!**
| Option | How | Best For |
|--------|-----|----------|
| **Local SAST** | `npx opengrep scan .` | Quick code analysis |
| **Dependency check** | `npm audit` or `trivy fs .` | Known vulnerabilities |
| **Web scanner** | Visit scanner.vibeship.co | Full GitHub repo scan |
| **Restart** | Close/reopen Claude Code | Connection issues |
**Want me to run a local scan instead?** I can use opengrep or npm audit right now.
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.
- 3d ago First seen · 209 lines · 12 tokens per session scan A adcb9b724299
scan is a command published in the GitHub repository vibeforge1111/vibeship-plugin (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,294 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.