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/statusgit 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/status)<a href="https://agentmods.dev/commands/vibeforge1111/vibeship-plugin/status"><img src="https://agentmods.dev/badge/commands/vibeforge1111/vibeship-plugin/status.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.01018 |
| Opus 5 | $0.00006 | $0.00509 |
| Sonnet 5 | $0.00002 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
status scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Run `curl https://mcp.vibeship.co/health` How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibeship Status Check
The user wants to see what's being remembered about their project. Show them a clear overview.
Step 1: Get Memory Status
Call mind_status() to check the health of local memory.
Step 2: Get Session State
Call mind_session() to get:
- Current goal
- Current approach
- Active blockers
- Rejected approaches
- Working assumptions
- Recent discoveries
Step 3: Get Spawner Project Status
Call spawner_orchestrate with minimal context to see what the cloud remembers:
- Project recognition
- Loaded skills
- Loaded rules
Step 4: Present Status Clearly
Format the response like this:
## 🧠 Your Project Memory
**Project**: [name from spawner or mind]
**Goal**: [goal from mind session]
**Stack**: [detected stack]
### Local Memory (Mind)
- Decisions remembered: X
- Learnings captured: X
- Problems documented: X
- Memory health: [healthy/needs attention]
### Cloud Memory (Spawner)
- Skills loaded: [list]
- Rules active: [list]
- Project ID: [id]
### Current Session
- Blockers: [list or "None"]
- Assumptions: [list or "None"]
- Last activity: [timestamp]
Step 5: Offer Actions
If there are issues, suggest fixes:
- "Your local memory is getting large. Want me to summarize old entries?"
- "No goal is set for this session. What are you working on?"
- "You have 3 unresolved blockers. Want to tackle them?"
Keep It Actionable
The status check should lead to action, not just information. Always end with:
- What's going well
- What needs attention
- A suggested next step
Handling Errors
If Mind status fails:
## Local Memory Status Unknown
**What happened:** Couldn't connect to memory service.
**What I can tell you:**
- Check if `.mind/` folder exists in your project
- If it exists, your memories are safe (just can't read them right now)
- If it doesn't exist, run `/vibeship-init` to set up
**Quick fix:** Restart Claude Code and try `/vibeship-status` again.
**In the meantime:** What are you working on? I can still help!
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 · 183 lines · 12 tokens per session scan A e3aed413a6f3
status 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,018 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.