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 rajitsaha/100xprism --skill context-dumpgit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/context-dump)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/context-dump"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/context-dump/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/rajitsaha/100xprism/context-dump"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/context-dump.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 8 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00059 | $0.00394 |
| Opus 5.5 | $0.00024 | $0.00158 |
| Sonnet 5.5 | $0.00012 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
context-dump 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 1mo 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 — Session Orientation Dump
Pull 7 days of git and GitHub activity into a structured summary. Run at the start of a session before making changes.
How to use
/context— full 7-day dump/context focus: <area>— limit to specific feature area or last PR
Phase 1 — Gather activity
PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
# Recent commits
git log --since="7 days ago" --oneline --all
# Open PRs
gh pr list --state open
# Merged PRs (last 10)
gh pr list --state merged --limit 10
# Open issues
gh issue list --state open
# CI health
gh run list --limit 3
Phase 2 — Produce summary
## Context Dump — [DATE]
### What shipped this week
- [merged PRs, 1-line summary of what changed]
### What's in flight
- [open PRs, status, blockers]
### Open issues
- [bugs / features, prioritized by recency]
### Recent commits (7 days)
- [key commits grouped by feature area]
### CI health
- [pass/fail, any flaky tests]
### Suggested next actions
- [based on above, what needs attention first]
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.
- 1mo ago First seen · 68 lines · 59 tokens per session scan A 46db2c3a5af0
context-dump is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 6d ago), licensed MIT. It adds 59 tokens to every session and 394 once invoked, about $0.0002 per session on Opus 5.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
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.