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/mr-remon219/search-boost/commit-authorshipgit clone --depth 1 https://github.com/Mr-remon219/search-boostWhat 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.00134 | $0.00134 |
| Opus 5 | $0.00067 | $0.00067 |
| Sonnet 5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
commit-authorship 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
Commit authorship
When committing in this repo:
- Author and committer must be the human maintainer (Mr-remon219 / [email protected]), not Cursor Agent or
[email protected]. - Never add
Co-authored-by:lines for Cursor, Cursor Agent, or any AI tool. - Do not use inverted co-author trailers; the user is the sole author even when an agent wrote the patch.
Prefer git commit with the user's configured identity and a message only; no agent attribution footers.
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 · 16 lines · 134 tokens per session scan A 0199f8d28e96
commit-authorship is a cursor rule published in the GitHub repository Mr-remon219/search-boost (5 stars, last pushed 14d ago), licensed MIT. It adds 134 tokens to every session, about $0.0007 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
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
react-best-practices
USE WHEN: Designing React components, implementing hooks, and managing component lifecycles.
performance
USE WHEN: Optimizing Core Web Vitals, managing assets, and ensuring high Lighthouse/A11y scores.
marker-insights
Aggregate Marker.io website feedback into recurring patterns. Use when asked to find the most common issues on a site, which pages get the most feedback, recurring content problems, or the content-vs-bug split across many Marker.io reports, and produce a prioritized brief for a website team or agency. Read-only: it…
cursorrules
Universal Long-Term Memory & Cross-Agent Handoff Protocol for AI Coding Agents.
agent-stories
Agent-optimized user story format — XML-tagged stories for AI coding agents. Use when writing backlog stories for implementation.