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 rsts-dev/claude-buddy-marketplace --skill primegit clone --depth 1 https://github.com/rsts-dev/claude-buddy-marketplaceWrote 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/rsts-dev/claude-buddy-marketplace/prime)<a href="https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/prime"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/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/rsts-dev/claude-buddy-marketplace/prime"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/prime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.00450 |
| Opus 5 | $0.00043 | $0.00225 |
| Sonnet 5 | $0.00017 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
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 11d 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.
What it actually says
Prime
Establish shared understanding before planning: pull the ticket and docs, map the codebase, and report what needs doing and how the code is organized. Priming a fresh session first is the discipline that keeps later steps grounded.
Customization
Before executing, check ~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Prime/PREFERENCES.md. If present, load and apply it; otherwise use defaults.
Prerequisites
- buddy + LifeOS installed (
test -f ~/.claude/LIFEOS/VERSION). - Foundation at
/directive/foundation.md(run/sdlc:initif missing).CLAUDE.mdis read if present. - MCP (recommended): Atlassian server for Jira/Confluence. Without it, paste the ticket text or pass a local file; Prime degrades gracefully and says so.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| PrimeContext | Any /sdlc:prime invocation |
Workflows/PrimeContext.md |
Output
A priming report (to the conversation). Optionally persisted to specs/<slug>/research.md when a spec folder exists.
Examples
User: "/sdlc:prime ABC-123"
→ Fetches Jira ABC-123 (summary, description, acceptance criteria) via Atlassian MCP
→ Follows any linked Confluence page
→ Maps the codebase (git ls-files, entry points, recent commits, foundation, CLAUDE.md)
→ Reports task context + tech stack + where the work lands + open questions
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 39 lines · 85 tokens per session scan A 79ca17e3e86a
Prime is a skill published in the GitHub repository rsts-dev/claude-buddy-marketplace (17 stars, last pushed 20d ago), licensed MIT. It adds 85 tokens to every session and 450 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…