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/haroon966/pinky-cursor/08-install-from-urlgit clone --depth 1 https://github.com/Haroon966/pinky-cursorWrote 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/haroon966/pinky-cursor/08-install-from-url)<a href="https://agentmods.dev/rules/haroon966/pinky-cursor/08-install-from-url"><img src="https://agentmods.dev/badge/rules/haroon966/pinky-cursor/08-install-from-url.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.00355 | $0.00355 |
| Opus 5 | $0.00178 | $0.00178 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade C, and why
08-install-from-url scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
3. `rm -rf` the temp clone. What it actually says
Install from pinky-cursor URL
If the user shares the pinky-cursor GitHub repo and wants Pinky in this project:
- Clone kit to a temp dir only (never into this project as
pinky-cursor/). - Run
bash <temp>/pinky-cursor/install.shwith cwd = this project (add--with-uionly if they ask for UI UX Pro Max). rm -rfthe temp clone.- Keep only installer payload:
AGENTS.md,CLAUDE.md,.cursor/rules/,skills/, host skill dirs,docs/pinky-*.md, gitignored.pinky/scaffold (and UI files if--with-ui). - Ask phone channel: WhatsApp · Slack · skip. WhatsApp → ask owner number; give
doctor.sh→login.sh(user terminal QR) →watch.sh(keep open). Never run those yourself. Never MCP whatsapp + watch together. Then reopen chat if needed.
Never leave kit README, assets/, LICENSE, .github/, install.sh, scripts/, or adapters/ sources in the project. Never submodule this repo. Never commit .pinky/ secrets/sessions.
Full steps: docs/pinky-install-for-agents.md (after install) or kit INSTALL.md (on GitHub).
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 · 19 lines · 355 tokens per session scan C 84c7f9bbbf11
08-install-from-url is a cursor rule published in the GitHub repository Haroon966/pinky-cursor (4 stars, last pushed 27d ago), licensed MIT. It adds 355 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.