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 roedyrustam/vibes-plug --skill session-context-loadergit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/session-context-loader)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/session-context-loader"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/session-context-loader.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.00079 | $0.01057 |
| Opus 5 | $0.00039 | $0.00528 |
| Sonnet 5 | $0.00016 | $0.00211 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
session-context-loader 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Context Loader
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
This skill ensures that the AI agent is always aligned with the project's core documentation. At the beginning of every new conversation session, it automatically searches for and reads essential project context files (Tech Stack, PRD, Roadmap, Blueprint). This guarantees that development remains focused, directed, and strictly adheres to established requirements and architectural decisions.
Trigger Conditions
Activate this skill IMMEDIATELY when:
- It is the very first message of a new conversation session.
- The user says "start session", "initialize project", or "load context".
- The AI realizes it lacks the high-level context of the current repository.
Execution Protocol
When triggered, you MUST perform the following steps before answering the user's primary request or writing any code:
-
Locate Key Documentation Files: Use your file search tools (
list_dir,grep_search, orview_file) to look for the following files in the project root or.docs/folder:PRD.md(Product Requirements Document)ROADMAP.mdorROADMAP.txtBLUEPRINT.mdorARCHITECTURE.mdTECH_STACK.md,package.json,go.mod,Cargo.toml, orrequirements.txt(to identify the tech stack)
-
Read and Internalize Context:
- Read the contents of the found files.
- Understand the project's primary goal, current phase in the roadmap, architectural constraints (blueprint), and the specific tech stack being used.
-
Acknowledge and Align:
- Briefly acknowledge to the user that the project context has been loaded successfully.
- State the current Tech Stack and the immediate goal based on the Roadmap/PRD.
- Proceed with addressing the user's actual request using the newly loaded 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.
- 3d ago First seen · 84 lines · 79 tokens per session scan A 15c0e9ac8734
session-context-loader is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 1,057 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-09-03.
Other skills, from other repositories
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
produck-feedback
Use when acting on real user feedback — you have a Produck feedback ticket or URL, or the user wants to fix something users complained about or build a feature users asked for. Pulls full feedback context through the Produck MCP and drives a feedback → aligned PRD → build loop. Triggers on "fix what users reported", a…
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".