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/strelov1/freehire/commit-checksgit clone --depth 1 https://github.com/strelov1/freehireWhat 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.00175 | $0.00175 |
| Opus 5 | $0.00088 | $0.00088 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
commit-checks 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
Before committing Go
When creating a git commit that includes any *.go file:
gofmt -wthose paths.gofmt -l .must print nothing.go vet ./...go test ./...(unit tests only — no-tags=integration).
Do not commit if vet or tests fail; fix first.
Skip this suite when the commit has no Go files (docs, OpenSpec, web-only).
Do not run go test -tags=integration ./... at commit time. That stays push-time: go vet -tags=integration ./... before every push; the full tagged suite when behaviour changed.
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 · 19 lines · 175 tokens per session scan A 1f449adea427
commit-checks is a cursor rule published in the GitHub repository strelov1/freehire (533 stars, last pushed 3d ago), licensed MIT. It adds 175 tokens to every session, about $0.0009 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
airtable-integration
Bordful uses Airtable as its backend database, providing a no-code solution for managing job listings with a user-friendly interface.
app-router-structure
Bordful uses Next.js 15 with the App Router for file-based routing. Understanding this structure is crucial for navigation and adding new features.
autofix
Please use the Playwright MCP to open a browser to the URL I provide, check for any errors, and then automatically fix those errors in my codebase, then continue to iterate until all the errors are gone.
cursorrules
Read and follow all instructions in INSTRUCTIONS.md at the repository root.
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.