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.
git 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/rules/rajitsaha/100xprism/context-dump)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/context-dump"><img src="https://agentmods.dev/badge/rules/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/rules/rajitsaha/100xprism/context-dump"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/context-dump.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.00024 | $0.00360 |
| Opus 5.5 | $0.00010 | $0.00144 |
| Sonnet 5.5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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
Suggested model tier: fast / low-cost (mechanical task)
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 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 · 67 lines · 24 tokens per session scan A f344b32f4c69
context-dump is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 360 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.