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/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/json-no-pretty-print)<a href="https://agentmods.dev/rules/jamie-bitflight/claude_skills/json-no-pretty-print"><img src="https://agentmods.dev/badge/rules/jamie-bitflight/claude_skills/json-no-pretty-print/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/jamie-bitflight/claude_skills/json-no-pretty-print"><img src="https://agentmods.dev/badge/rules/jamie-bitflight/claude_skills/json-no-pretty-print.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.00259 | $0.00259 |
| Opus 5 | $0.00130 | $0.00130 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
json-no-pretty-print 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 6d 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
JSON output (no pretty-print by default)
Scope: JSON a program emits at runtime — script stdout, CLI results, MCP tool payloads, API responses, generated report files. Anything a process prints or writes for another program or an LLM to parse.
- Emit compact JSON:
JSON.stringify(value),json.dumps(data),model_dump_json(). NeverJSON.stringify(value, null, 2), neverindent=. - Indentation and newlines are token cost for a model and add no parsing benefit.
Out of scope: JSON files committed to the repository as configuration or data — package.json,
tsconfig.json, biome.json, every harness plugin manifest (.claude-plugin/plugin.json,
.codex-plugin/plugin.json, .cursor-plugin/plugin.json), marketplace.json, test fixtures,
snapshots. Humans read and edit these, git diffs them line by line, and non-AI tooling consumes
them. Keep their existing pretty-printed formatting. Never reformat one as part of an unrelated
change, and never cite this rule to justify compacting one.
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.
- 6d ago First seen · 22 lines · 259 tokens per session scan A cb8b6de58f29
json-no-pretty-print is a cursor rule published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed yesterday), licensed MIT. It adds 259 tokens to every session, about $0.0013 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.