Borrowing it
Nothing to install: this file belongs to Tiimie1/claude-bell. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tiimie1/claude-bell/main/CLAUDE.mdgit clone --depth 1 https://github.com/Tiimie1/claude-bellWrote 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/instructions/tiimie1/claude-bell/claude-md)<a href="https://agentmods.dev/instructions/tiimie1/claude-bell/claude-md"><img src="https://agentmods.dev/badge/instructions/tiimie1/claude-bell/claude-md/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/instructions/tiimie1/claude-bell/claude-md"><img src="https://agentmods.dev/badge/instructions/tiimie1/claude-bell/claude-md.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.00477 | $0.00477 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
claude-bell CLAUDE.md 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 9d 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
Git
Always do git add . and check if there are some things that shouldn't be committed (if so add them to gitignore). than create commits and branch based on all the changes made.
Git branches
Use Prefixes to Indicate Purpose. Use kebab-case. Branch names should be concise yet informative. A good branch name briefly describes what it is for without being overly long or vague.
feat:- For new features or functionalities.bug:- For fixing bugs in the code.hotfix:- For urgent patches, usually applied to production.refactor:- For improving code structure without changing functionality.test:- For writing or improving automated tests.doc:- For documentation updates.
Examples:
feature/user-authentication
bugfix/fix-login-error
hotfix/urgent-patch-crash
design/update-navbar
refactor/remove-unused-code
test/add-unit-tests
doc/update-readme
Git Commits
Use conventional commit prefixes for all commit messages:
feat:- New features or functionalityfix:- Bug fixesrefactor:- Code refactoring without changing functionalitychore:- Maintenance tasks, dependency updates, config changescicd:- CI/CD pipeline changes
Example: feat: add dark mode toggle
Releasing (GoReleaser + Homebrew)
To publish a new release and update the Homebrew tap (Tiimie1/homebrew-tap):
-
Tag the release (GoReleaser derives the version from git tags):
git tag -a v0.x.x -m "Release v0.x.x" git push origin v0.x.x -
Run GoReleaser (requires a
GITHUB_TOKENwith repo write access):GITHUB_TOKEN=<your-token> goreleaser release --cleanIf the token is already exported in your shell, just run:
goreleaser release --clean
GoReleaser will build binaries for darwin amd64/arm64, create a GitHub release, and push the updated formula to the Homebrew tap automatically.
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.
- 9d ago First seen · 57 lines · 477 tokens per session scan A 24d0dcf9beeb
claude-bell CLAUDE.md is an instructions file published in the GitHub repository Tiimie1/claude-bell (22 stars, last pushed 6mo ago), licensed MIT. It adds 477 tokens to every session, about $0.0024 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 instructions, from other repositories
skill-doctor git-workflow.instructions.md
Instructions for evilstar2016/skill-doctor, covering git-workflow, description, when to use and instructions.
skill-doctor github-automation.instructions.md
Instructions for evilstar2016/skill-doctor, covering github-automation, description, when to use and instructions.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).