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/OrlojHQ/orlojWrote 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/orlojhq/orloj/changelog)<a href="https://agentmods.dev/rules/orlojhq/orloj/changelog"><img src="https://agentmods.dev/badge/rules/orlojhq/orloj/changelog.svg" alt="Measured on agentmods" 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.00196 | $0.00196 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
changelog 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 8d 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
Changelog
Shared agent guidance lives in .agents/rules.md. Keep this Cursor rule consistent with that file.
When a change affects users or operators (API, CLI, behavior, docs readers care about, examples, defaults), add a bullet under ## [Unreleased] in CHANGELOG.md in the right section: Added, Changed, Deprecated, Removed, Fixed, or Security.
Skip changelog entries for internal refactors, test-only changes, and CI/tooling that does not change user-visible behavior. Full policy: CONTRIBUTING.md (section Changelog).
If the PR already has a suitable [Unreleased] entry, do not duplicate; extend it.
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.
- 8d ago First seen · 15 lines · 196 tokens per session scan A 8e6a29476532
changelog is a cursor rule published in the GitHub repository OrlojHQ/orloj (118 stars, last pushed 3d ago), licensed Apache-2.0. It adds 196 tokens to every session, about $0.0010 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
git-author
Git author identity for commits so GitHub attributes contributions correctly.
commit-and-push
Commit (conventional commit) files and push to the remote repository.
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
git
Git commit, branch, and PR conventions for this repository.
04-review-and-commit
Review, completion, and commit workflow.
conventional-commits
Always use Conventional Commits for git commit messages.