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/peak-studios/peak-agent-toolkit/peak-scriptsgit clone --depth 1 https://github.com/Peak-Studios/peak-agent-toolkitWhat 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.00000 | $0.00108 |
| Opus 5 | $0.00000 | $0.00054 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
peak-scripts 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.
What it actually says
Use the Peak Studios MCP server at https://peak-agent-toolkit.vercel.app/mcp or catalog/catalog.json. Inspect the installed version before editing. Cite indexed public documentation, label inference, preserve optional dependencies, and never invent exports, events, configuration keys, or private implementation details.
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 · 9 lines · 0 tokens per session scan A 3ef96a76abbc
peak-scripts is a cursor rule published in the GitHub repository Peak-Studios/peak-agent-toolkit (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 108 tokens. 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-08-31.
Other cursor rules, from other repositories
cursorrules
You are working on CFX Developer Tools, a Cursor IDE plugin for FiveM and RedM resource development.
cfx-lua-conventions
Coding conventions for Lua scripts in FiveM and RedM resources.
cfx-javascript-conventions
Coding conventions for JavaScript scripts in FiveM and RedM resources.
performance-rules
Performance optimization rules for CFX resources.
fxmanifest-standards
Standards for FiveM/RedM resource manifest files.
security-best-practices
Security rules for FiveM/RedM resource development.