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/techdebt)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/techdebt"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/techdebt.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.1 | $0.00020 | $0.00484 |
| Opus 5 | $0.00010 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
techdebt 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 3d 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: balanced (moderate reasoning)
Techdebt — Technical Debt Scanner
Scan the codebase for technical debt and eliminate it. Run at end of session or when the codebase feels bloated.
Do NOT ask for permission — scan, report, then ask before fixing.
How to use
/techdebt— full scan + report, confirm before fixing/techdebt fix— scan and fix without confirmation
Phase 1 — Scan
PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
Look for:
- Duplicated code — copy-pasted logic that should be a shared utility
- Dead code — unused functions, variables, imports, exports, commented-out blocks
- Redundant abstractions — over-engineered helpers used in only one place
- Inconsistent patterns — same operation done 3+ different ways across files
- Stale TODOs / FIXMEs — old comments no longer relevant
Use Grep and Glob to identify candidates. Confirm each item is truly dead/duplicated before reporting.
Phase 2 — Report
## Tech Debt Found
### Duplicated Code
- `src/utils/formatDate.ts:12` and `src/helpers/dates.ts:45` — identical logic
Fix: consolidate into formatDate.ts, delete dates.ts
### Dead Code
- `src/api/legacyAuth.ts` — no imports found anywhere
Fix: delete file
### Stale TODOs
- `src/components/Modal.tsx:89` — TODO from 6 months ago, feature shipped
Fix: remove comment
Phase 3 — Fix (with confirmation)
For each item, ask the user to confirm unless they said "fix". After fixes:
# Run tests to verify nothing broke
npm test 2>&1 | tail -20
GATE: Tests still pass after cleanup.
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.
- 3d ago First seen · 71 lines · 20 tokens per session scan A 90da6f8857bd
techdebt is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 484 once invoked, about $0.0001 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.