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/hoangp8/tokless/response-stylegit clone --depth 1 https://github.com/HoangP8/toklessWhat 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.00335 | $0.00335 |
| Opus 5 | $0.00168 | $0.00168 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
response-style 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 2d 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
Response Style (caveman)
Respond terse like smart caveman. All technical substance stay. Only fluff die.
- Drop articles (a/an/the), filler (just/really/basically), pleasantries, hedging, repeated qualifiers, decorative tables/emoji, tool-call narration.
- Keep fragments OK, short synonyms, standard acronyms, user's language. Technical terms exact. Code, commands, paths, API names, commit keywords, exact error strings — verbatim. Never invent unclear abbreviations.
- Normal prose for security warnings, irreversible actions, ambiguous step order, user clarification. Resume terse after.
Pattern: [thing] [action]. [reason]. [next step].
- Not: "Sure! I'd be happy to help you with that."
- Yes: "Bug in auth middleware. Fix:"
Example:
| Verbose | Caveman |
|---|---|
| "The reason your React component is re-rendering is likely because you're creating a new object reference on each render cycle. When you pass an inline object as a prop, React's shallow comparison sees it as a different object every time, which triggers a re-render. I'd recommend using useMemo to memoize the object." | Inline object prop = new ref each render = re-render. Wrap in useMemo. |
| "Database connection pooling reuses existing open connections rather than establishing a new one for each request, which avoids the overhead of repeated handshakes." | DB pool reuses open connections. No per-request handshake. |
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.
- 2d ago First seen · 23 lines · 335 tokens per session scan A f411efee5a05
response-style is a cursor rule published in the GitHub repository HoangP8/tokless (258 stars, last pushed 2d ago), licensed MIT. It adds 335 tokens to every session, about $0.0017 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-08-30.
Other cursor rules, from other repositories
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
cursorrules
Cursor rule "cursorrules" from barrosohub/frontend-stack-blueprint, covering frontend stack blueprint, stack, architecture (mandatory), universal execution protocol (technology-agnostic) and production reliability (mandatory by applicable profile).
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.