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/jacoby6000/smithplates/linting-and-formattinggit clone --depth 1 https://github.com/Jacoby6000/SmithplatesWrote this? Show the measurements
A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/rules/jacoby6000/smithplates/linting-and-formatting)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 | $0.00163 | $0.00163 |
| Opus 5 | $0.00081 | $0.00081 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
linting-and-formatting 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
Linting & Formatting
Linting and Formatting should be configured for every code project so that formatting discussions can be kept out of PR discussion. Formatting and linting should be left to the tools. Precommit should be configured to run linters and formatters prior to push, and CI should validate lint/format.
In practice, every project must have:
- A committed formatter + linter config (e.g. rustfmt/clippy, prettier/eslint, ruff/black) checked into the repo.
- A pre-commit hook that runs the formatter and linter before push.
- A CI check that fails the build on any formatting or lint violation.
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 · 18 lines · 163 tokens per session scan A 48c68299a8bd
linting-and-formatting is a cursor rule published in the GitHub repository Jacoby6000/Smithplates (2 stars, last pushed 22d ago), licensed MIT. It adds 163 tokens to every session, about $0.0008 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-31.
Other cursor rules, from other repositories
40-deploy
For PM2 processes, GitHub Actions, health checks, and production operations.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
github-actions
GitHub Actions workflow guidelines.
devops-infrastructure
DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD. Load when editing Dockerfiles, compose, k8s manifests, Terraform, or workflow YAML — not for application code.
workflow-ci
Testing and verification workflow expectations.
ci-scripts-maintenance
CI and script maintenance after software updates.