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/reddy-sh/tokenHUDWrote 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/reddy-sh/tokenhud/no-tool-contributors)<a href="https://agentmods.dev/rules/reddy-sh/tokenhud/no-tool-contributors"><img src="https://agentmods.dev/badge/rules/reddy-sh/tokenhud/no-tool-contributors/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/reddy-sh/tokenhud/no-tool-contributors"><img src="https://agentmods.dev/badge/rules/reddy-sh/tokenhud/no-tool-contributors.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.00104 | $0.00104 |
| Opus 5.5 | $0.00042 | $0.00042 |
| Sonnet 5.5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
no-tool-contributors 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 2mo 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
No Third-Party Tool Contributors
Never add third-party coding tools (Devin, Claude, Copilot, Cursor, etc.) as contributors or co-authors in git commits.
- Do NOT include
Co-Authored-Bytrailers for any AI tool or bot - Do NOT include
Generated with [Tool]lines in commit messages - Commits should only attribute the human developer
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.
- 2mo ago First seen · 13 lines · 104 tokens per session scan A 39c412fb1566
no-tool-contributors is a cursor rule published in the GitHub repository reddy-sh/tokenHUD (2 stars, last pushed 2mo ago), licensed MIT. It adds 104 tokens to every session, about $0.0004 per session on Opus 5.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
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
commit-message-format
A rule for writing Git commit messages in a standard format, such as `fix: correct login error` or `feat(api): add search`. A commit message records what a code change contains.
conventional-commits
Conventional Commits mapped to SemVer; use this repo's types and scopes for commit and PR titles.
atomic-commits
Git best practices - atomic commits, descriptive messages, feature branches.