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 rules/rajitsaha/100xprism/commitgit 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/commit)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/commit"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/commit.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 | $0.01531 | $0.01531 |
| Opus 5 | $0.00766 | $0.00766 |
| Sonnet 5 | $0.00306 | $0.00306 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
commit 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 yesterday.
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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit — Gate → Stage → Commit
Quality gate runs FIRST. Do NOT commit if any gate fails. Do NOT ask for permission or skip the gate.
Phase 0 — Quality Gate (MANDATORY)
Check gate cache first — skip if it already passed for this exact tree state. The cache is keyed on a tree token (HEAD + tracked diff + untracked files), not a bare HEAD, so a dirty or rebased tree never reuses a stale pass:
TOKEN=$(python3 ~/100xprism/hooks/gate-pass.py --print 2>/dev/null)
CACHED=$(cat ~/.100xprism/gate-cache 2>/dev/null)
[ -n "$TOKEN" ] && [ "$CACHED" = "$TOKEN" ] && echo "Gate: skipped (already passed for this tree)" && GATE_DONE=true || GATE_DONE=false
If GATE_DONE=false: run the gate workflow. On pass, record it (same token the
gate-on-commit hook checks):
python3 ~/100xprism/hooks/gate-pass.py
Do NOT proceed until gate reports ✅ ALL GATES PASSED. If any gate fails → STOP, fix, clear cache, re-run gate.
Phase 1 — Review changes
PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
git status
git diff --stat
git diff --name-only HEAD 2>/dev/null || true
Phase 2 — Update docs (if needed)
Based on what changed, update corresponding documentation:
| Changed files | Doc to update |
|---|---|
| API routes or handlers | API reference doc (README, project instruction file, or docs/) |
| CLI commands or flags | CLI reference doc |
| New features or config | README.md or project-equivalent |
| Removed files/features | Remove stale references from all docs |
.claude/commands/** |
No doc update needed |
Read the project instruction file for specific doc file paths. Skip if no docs are affected.
Phase 3 — Stage files
Stage only task-related files. Never stage .env, dist/, node_modules/, venv/, unrelated work:
git add -u
# Or stage specific files if -u picks up unrelated changes:
# git add path/to/file1 path/to/file2
git diff --staged --stat
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.
- yesterday First seen · 191 lines · 1,531 tokens per session scan A 69ade6afc789
commit is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 4d ago), licensed MIT. It adds 1,531 tokens to every session, about $0.0077 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 cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.