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 Mburdo/knowledge_and_vibes --skill primegit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWrote 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/mburdo/knowledge_and_vibes/prime)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/prime"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/prime/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/mburdo/knowledge_and_vibes/prime"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/prime.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.01633 |
| Opus 5.5 | $0.00017 | $0.00653 |
| Sonnet 5.5 | $0.00008 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
prime 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prime — Session Startup
Complete startup checklist for new agent sessions. Direct execution (no subagents).
Design rationale: This skill executes directly rather than spawning subagents because each step is a simple command sequence (~200 tokens each), not substantial analytical work. Per Lita research: "Simple agents achieve 97% of complex system performance with 15x less code." Subagent overhead would exceed actual work.
When This Applies
| Signal | Action |
|---|---|
| New session starting | Run full checklist |
| User says "/prime" | Run full checklist |
| User says "startup" or "initialize" | Run full checklist |
| Multi-agent coordination needed | Run full checklist |
Tool Reference
Agent Mail (MCP)
| Tool | Purpose |
|---|---|
macro_start_session(human_key, program, model) |
PREFERRED: All-in-one startup |
ensure_project(human_key) |
Initialize project in Agent Mail |
register_agent(project_key, program, model) |
Register and get agent name |
set_contact_policy(agent_name, policy) |
Set to "open" for coordination |
fetch_inbox(agent_name, limit) |
Check for messages |
send_message(to, subject, body_md) |
Send greeting/announcements |
Bash Commands
| Command | Purpose |
|---|---|
cm context "task description" --json |
Get patterns + anti-patterns before work |
cass search "query" --robot --days 7 |
Search session history |
bd ready --json |
List available tasks |
bv --robot-triage |
Get task recommendations |
git status |
Check repo state |
git log --oneline -5 |
Recent commits |
Execution Flow
Execute these steps directly. No subagents needed.
Step 1: Register Identity
PREFERRED — Use macro for simplicity:
result = macro_start_session(
human_key="PROJECT_PATH", # Absolute path to project
program="claude-code",
model="opus-4.5",
inbox_limit=10
)
agent_name = result["agent"]["name"] # e.g., "BlueLake"
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 · 272 lines · 42 tokens per session scan A 21f6d7d149c3
prime is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 9mo ago), licensed MIT. It adds 42 tokens to every session and 1,633 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.