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/terminal-setup)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/terminal-setup"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/terminal-setup/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/terminal-setup"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/terminal-setup.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.00030 | $0.00439 |
| Opus 5 | $0.00015 | $0.00219 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
terminal-setup 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 5d 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
Configure your terminal environment for maximum Claude Code productivity.
Recommended Setup
Terminal: Ghostty
- Synchronized rendering, 24-bit color, proper unicode support
- Color-code and name terminal tabs for context (e.g., "frontend", "api", "tests")
- One tab per task or git worktree
Status Bar: /statusline
Run /statusline to configure your status bar to always show:
- Current context token usage
- Current git branch
- Active task / worktree name
This prevents context overload surprises mid-session.
Tmux for Parallel Worktrees
- One tmux window per Claude task/worktree
- Name windows after the task:
tmux rename-window "auth-refactor" - Lets you switch between parallel Claude sessions without losing context
Voice Dictation
- You speak 3x faster than you type
- Voice-dictated prompts are more detailed and natural → better Claude output
- macOS: press
fn fn(double-tap fn key) to activate dictation anywhere - Use voice for long context dumps, specs, and bug descriptions
Quick Setup Checklist
- Install Ghostty (or iTerm2 with 24-bit color)
- Run
/statuslineto enable token + branch display - Set up tmux with one window per active task
- Enable macOS voice dictation (
System Settings → Keyboard → Dictation) - Color-code tabs by domain (frontend=blue, api=green, infra=red)
Tips
- Before starting a large task: open a new tmux window, name it, start fresh
- Use
ctrl+bin tmux to run Claude agents in background - The status line's context counter tells you when to
/compactor start fresh
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.
- 5d ago First seen · 49 lines · 30 tokens per session scan A 2367d458e3bd
terminal-setup is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 439 once invoked, about $0.0002 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
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.
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.