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 instructions/vibeforge1111/vibeship-plugin/claude-mdgit 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/instructions/vibeforge1111/vibeship-plugin/claude-md)<a href="https://agentmods.dev/instructions/vibeforge1111/vibeship-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/vibeforge1111/vibeship-plugin/claude-md.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.1 | $0.01055 | $0.01055 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
vibeship-plugin CLAUDE.md 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory (Mind)
This project uses Mind for persistent memory across sessions.
Required Protocol
-
Session Start: ALWAYS call
mind_recall()before responding to the first message. This loads context from previous sessions. -
During Work: Use
mind_log(message, type)to capture what happens:mind_log("chose X over Y - simpler", type="decision")→ MEMORY.mdmind_log("API returns 500 on large payloads", type="problem")→ MEMORY.mdmind_log("Safari needs vendor prefix for X", type="learning")→ MEMORY.mdmind_log("resolved by increasing timeout", type="progress")→ MEMORY.mdmind_log("working on auth flow", type="experience")→ SESSION.mdmind_log("build keeps failing", type="blocker")→ SESSION.mdmind_log("tried Redis - too complex", type="rejected")→ SESSION.mdmind_log("assuming user has stable internet", type="assumption")→ SESSION.md
-
Session End: Summarize with
## DATE | what happened | mood: X
Two-Layer Memory
MEMORY.md (permanent, cross-session):
- Decisions, learnings, problems, progress
- Use types:
decision,learning,problem,progress
SESSION.md (ephemeral, within-session):
- Raw experience, blockers, rejected approaches, assumptions
- Use types:
experience,blocker,rejected,assumption - Valuable items get promoted to MEMORY.md on session gap (>30 min)
Tools Available
mind_recall()- Load session context (CALL FIRST!)mind_log(msg, type)- Log to session or memory (routes by type)mind_session()- Get current session statemind_blocker(description)- Log blocker + auto-search memory for solutionsmind_search(query)- Find specific memoriesmind_remind(msg, when)- Set time or context remindermind_checkpoint()- Force process pending memoriesmind_edges(intent)- Check for gotchas before codingmind_status()- Check memory health
Stack
(not detected)
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.
- 5d ago First seen · 102 lines · 1,055 tokens per session scan A fe5e34e3b3a5
vibeship-plugin CLAUDE.md is an instructions file published in the GitHub repository vibeforge1111/vibeship-plugin (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 1,055 tokens to every session, about $0.0053 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 instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.