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/lucassantana-dev/sharekit/context-packnpx skills add LucasSantana-Dev/sharekit --skill context-packgit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWhat 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.00128 | $0.00467 |
| Opus 5 | $0.00064 | $0.00234 |
| Sonnet 5 | $0.00026 | $0.00093 |
| Haiku 4.5 | $0.00013 | $0.00047 |
Grade A, and why
context-pack 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 2d 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
context-pack
Use before reading broadly.
Goal
Pull only the code, standards, plans, and notes that matter for the task.
Done when: context bundle complete and next read would not change action.
Preferred sources (in order)
See references/discovery-strategy.md §Preferred sources.
See also standards/user-context.md — context load order (repo state → handoff → plan → memory → standards).
Rules
See references/discovery-strategy.md §Symbol lookup strategy, §Chunking discipline, and §Anti-patterns for task-scoped retrieval rules.
Failure / Stop Conditions
- Mount guard: If External HD unmounted →
rag_querydegrades; fall back to grep + claude-mem. Check before starting:mount | grep -q "${DEV_ROOT}" || echo "BLOCKED: External HD unmounted — RAG/vault unreachable". - If RAG retrieval returns nothing and no plans/handoffs exist for the topic → read the 2-3 most relevant files directly; do not expand the read set speculatively.
- Stop accumulating context when the next read would not change the action — marginal reads waste budget and dilute signal.
- Do not invoke context-pack for tasks touching one known file; direct read is faster.
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.
- 2d ago First seen · 43 lines · 128 tokens per session scan A 5764b38d9381
context-pack is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 2d ago), licensed MIT. It adds 128 tokens to every session and 467 once invoked, about $0.0006 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-31.
Other skills, from other repositories
prpm-development
Use when developing PRPM (Prompt Package Manager) - comprehensive knowledge base covering architecture, format conversion, package types, collections, quality standards, testing, and deployment.
creating-cursor-rules-skill
Expert guidance for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-opencode-plugins
Use when creating OpenCode plugins that hook into command, file, LSP, message, permission, server, session, todo, tool, or TUI events - provides plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript event-driven modules.
creating-kiro-packages
Use when creating Kiro steering files or hooks - provides inclusion modes (always/fileMatch/manual), foundational files (product.md/tech.md/structure.md), and JSON hook configuration with event triggers.
creating-continue-packages
Use when creating Continue rules - provides required name field, alwaysApply semantics, glob/regex patterns, and markdown format with optional frontmatter.
thoroughness
Use when implementing complex multi-step tasks, fixing critical bugs, or when quality and completeness matter more than speed - ensures comprehensive implementation without shortcuts through systematic analysis, implementation, and verification phases.