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 ohad6k/VibeRaven --skill production-contextgit clone --depth 1 https://github.com/ohad6k/VibeRavenWrote 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/ohad6k/viberaven/production-context)<a href="https://agentmods.dev/skills/ohad6k/viberaven/production-context"><img src="https://agentmods.dev/badge/skills/ohad6k/viberaven/production-context/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/ohad6k/viberaven/production-context"><img src="https://agentmods.dev/badge/skills/ohad6k/viberaven/production-context.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.00048 | $0.00586 |
| Opus 5 | $0.00024 | $0.00293 |
| Sonnet 5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
production-context 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeRaven: Production Context
Repo context says what exists. Production context says what is dangerous.
Hard Rule
Keep memory small enough to reuse in the next agent action. Do not create a report dump.
File
Maintain:
.viberaven/production-context.md
Create it when allowed and missing. Otherwise propose the exact entry.
Loop
read -> isolate risk -> fix/propose -> verify -> record -> open action
- Read the current file before production-sensitive work.
- Identify one relevant boundary: release, auth, data/RLS, provider dashboard, deploy/env, job/webhook, billing, storage, or customer path.
- Use repo evidence first: git status, tags, changelog, PR links, diffs, migrations, env examples, tests.
- Use VibeRaven/provider MCP evidence when available for provider state, release history, and dashboard-adjacent receipts.
- Record only what changes the next decision.
- Separate repo fixes from provider/human actions.
When the output names Next skill:, continue with that VibeRaven skill unless user input, auth, or provider proof is required.
Use Next skill: go-live when context is recorded and the next step is deploy/live proof. Use Next skill: what-broke when context shows a version/release regression. Use Next skill: architecture-context when the risk reveals an unclear product boundary.
File Shape
# VibeRaven Production Context
## Current Release / Change Window
## Recent Changes
## Architecture Boundaries
## Provider Boundaries
## Migration And Data History
## Incidents And Rollback Notes
## Fragile Customer Paths
## Verification Receipts
## Open Provider Or Human Actions
Entry Shape
### YYYY-MM-DD - short label
- Change:
- Evidence:
- Boundary:
- Danger:
- Repo fix:
- Verification:
- Provider/MCP proof:
- Open action:
Use unknown from repo when provider state is not proven.
Output
Context read:
Context updated/proposed:
Boundary:
Repo action:
Provider/MCP action:
Next skill:
Next:
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.
- 8d ago First seen · 92 lines · 48 tokens per session scan A aaccf50f0eee
production-context is a skill published in the GitHub repository ohad6k/VibeRaven (38 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 586 once invoked, about $0.0002 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
fullstack-ai-app-builder
A method for building and launching complete AI-powered web applications, from requirements and technical planning through the front end, back end, AI integration, and deployment. It is aimed at people who want to create an application without a back-end engineer.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
apollo-lead-finder
Two-phase Apollo.io prospecting: free People Search to discover ICP-matching leads, then selective enrichment to reveal emails/phones (credits per contact). Creates Apollo lists. Deduplicates against existing contacts by LinkedIn URL.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the brand-color canvas, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed at…