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 skills/omergocmen/vibe-coder-kit/project-context-primernpx skills add omergocmen/vibe-coder-kit --skill project-context-primergit clone --depth 1 https://github.com/omergocmen/vibe-coder-kitWrote 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/omergocmen/vibe-coder-kit/project-context-primer)<a href="https://agentmods.dev/skills/omergocmen/vibe-coder-kit/project-context-primer"><img src="https://agentmods.dev/badge/skills/omergocmen/vibe-coder-kit/project-context-primer.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.00058 | $0.01160 |
| Opus 5 | $0.00029 | $0.00580 |
| Sonnet 5 | $0.00012 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
project-context-primer 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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context Primer Skill
When to Trigger
Always run first when:
- Starting a new conversation about this project
- A subagent is spawned to work on a module
- Picking up work after a gap of more than a day
- Someone says "can you help with this project?" without any context
Step-by-Step Process
1. Load the Knowledge Index
Read .agent/knowledge/INDEX.md first.
The INDEX.md file contains rows in this format:
| Date | Type | Topic (linked) | One-line summary |
- Scan all rows for entries relevant to today's task
- For each relevant row, follow the link and read the full
.agent/knowledge/<slug>.mdfile - Pay special attention to entries of type
decisionandgotcha— these prevent the most costly mistakes - Extract the slug from the link:
[topic](./auth/token-refresh.md)→ slug isauth/token-refresh
If INDEX.md does not exist, output this exact warning and proceed:
⚠️ Knowledge base not initialized (.agent/knowledge/INDEX.md missing).
This means no architectural decisions, conventions, or gotchas have been recorded yet.
Action: Use the `knowledge-base-update` skill at the end of this session to start building it.
2. Load the Project README
Read README.md (or docs/README.md if present).
Extract and internalize:
- What the project does (one sentence)
- Tech stack (language, framework, major libraries)
- How to run it locally
- How to run tests
3. Load Active Task Context
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.
- 4d ago First seen · 154 lines · 58 tokens per session scan A 5e9e7fbf93d5
project-context-primer is a skill published in the GitHub repository omergocmen/vibe-coder-kit (91 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 1,160 once invoked, about $0.0003 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
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c-pro
Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.
performance-tester
Load testing, memory leak detection, benchmark analysis, and performance optimization. / TR: Yük (load) testi, memory leak (bellek kaçağı) tespiti, benchmark analizleri ve performans optimizasyonu.
adversarial-code-reviewer
Acts as a senior 'Devil's Advocate' code auditor inspecting showstoppers, memory leaks, unhandled exceptions, and security gaps before code delivery. / TR: Yazılan kodu teslim etmeden önce 'Şeytanın Avukatı' gözüyle gizli bug, showstopper, bellek kaçağı ve mimari açıkları arayan denetçi.
tdd
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/ /, verify APIs via web search, then implement in tiny test-verified steps.
electron-desktop-builder
Converts a web app (Express, React, Vite, Next.js) into an Electron desktop app. Use when starting a new Electron project from an existing web app, when setting up electron-builder for the first time, when creating main.ts/preload.ts boilerplate, when generating icon assets, or when configuring NSIS installers.…