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/bookedsolidtech/helixirWrote 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/bookedsolidtech/helixir/003-attribution)<a href="https://agentmods.dev/rules/bookedsolidtech/helixir/003-attribution"><img src="https://agentmods.dev/badge/rules/bookedsolidtech/helixir/003-attribution/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/bookedsolidtech/helixir/003-attribution"><img src="https://agentmods.dev/badge/rules/bookedsolidtech/helixir/003-attribution.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.00323 | $0.00323 |
| Opus 5.5 | $0.00129 | $0.00129 |
| Sonnet 5.5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
003-attribution 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- 003-attribution — 100% identical, 0 lines differ
What it actually says
No AI Attribution in Client-Facing Content
Do not expose AI tooling in client git history, PR descriptions, or code comments.
What to remove
Remove these patterns from all commits, PR bodies, commit messages, and code:
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>Co-Authored-By: Claude ...(any variant)Generated with Claude Code🤖 Generated with [Claude Code](https://claude.com/claude-code)claude.aireferences in commit messages or PR descriptions- AI assistant footers in PR templates
Enforcement
- commit-msg hook strips attribution automatically from every commit message
- This rule governs PR bodies and code comments, which the hook does not cover
- Before running
gh pr create, review the body — remove attribution strings manually
What's allowed
- Internal tooling notes in
.claude/config files (gitignored) - Documentation about the AI workflow in team-facing docs (e.g.,
CONTRIBUTING.md) when explicitly approved - Attribution in commits to internal/private BST repos where it's expected
Why
Client projects are delivered work product. AI tooling attribution in git history creates unnecessary disclosure, may violate NDA scope, and makes commits less professional. The work speaks for itself.
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.
- 1mo ago First seen · 37 lines · 323 tokens per session scan A 213cd48005f1
003-attribution is a cursor rule published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 323 tokens to every session, about $0.0013 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-workflow
Git workflow: commits, branches, PRs, history management.
ux-audit
UX audit and design guidance skill.
conventional-commits
Conventional Commits format enforced by pre-commit hooks.
pre-commit-lint-format
Run lint and format checks before every git commit.
commit-after-task
Ensure traceability, collaboration, and a clean project history by committing and pushing changes after completing each task.
git-workflow
Git workflow: commits, branches, PRs, history management.