Borrowing it
Nothing to install: this file belongs to dhruv-anand-aintech/agent-rules-sync. 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/dhruv-anand-aintech/agent-rules-sync/main/CLAUDE.mdgit clone --depth 1 https://github.com/dhruv-anand-aintech/agent-rules-syncWrote 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/dhruv-anand-aintech/agent-rules-sync/claude-md)<a href="https://agentmods.dev/instructions/dhruv-anand-aintech/agent-rules-sync/claude-md"><img src="https://agentmods.dev/badge/instructions/dhruv-anand-aintech/agent-rules-sync/claude-md.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.03509 | $0.03509 |
| Opus 5 | $0.01754 | $0.01754 |
| Sonnet 5 | $0.00702 | $0.00702 |
| Haiku 4.5 | $0.00351 | $0.00351 |
Grade C, and why
agent-rules-sync CLAUDE.md scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf dist/ build/ *.egg-info How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Rules Sync - Project Context
Quick Facts
- Project: Agent Rules Sync - Synchronize rules across AI coding assistants
- Language: Python 3.8+
- Main File:
agent_rules_sync.py(single-file module with daemon support) - Tests: Located in
tests/directory (29 tests, all passing) - Package: Published on PyPI - https://pypi.org/project/agent-rules-sync/
Release Workflow
1. Prepare Changes
- Make code changes and commit to git
- Run tests:
/usr/bin/python3 -m pytest tests/ -v - Ensure all tests pass before releasing
2. Version Bump
Update THREE files to bump version (e.g., from 1.2.2 to 1.2.3):
File 1: pyproject.toml (line 7)
version = "1.2.3"
File 2: CHANGELOG.md (add entry at top)
## [1.2.3] - 2026-02-07
### 🧪 Category Name
- Feature description 1
- Feature description 2
File 3: setup.py - NO CHANGE NEEDED
- It reads version from
pyproject.tomlautomatically
Commit the version bump:
git add pyproject.toml CHANGELOG.md
git commit -m "chore: bump version to 1.2.3 with [description]"
git push origin main
3. Build Package
# Clean old builds
rm -rf dist/ build/ *.egg-info
# Build wheel and sdist using miniforge python
python3.10 -m build
Output: dist/agent_rules_sync-1.2.3.tar.gz and dist/agent_rules_sync-1.2.3-py3-none-any.whl
4. Publish to PyPI
# Upgrade twine if needed
python3.10 -m pip install --upgrade twine
# Upload to PyPI (uses ~/.pypirc credentials)
python3.10 -m twine upload dist/agent_rules_sync-1.2.3* --skip-existing
Verify at: https://pypi.org/project/agent-rules-sync/
5. Create GitHub Release
# Create and push git tag
git tag -a v1.2.3 -m "test: add daemon watch detection tests"
git push origin v1.2.3
# Create GitHub release (with auto-generated notes)
gh release create v1.2.3 --title "v1.2.3: Test Coverage Improvements" --notes "Release notes here"
Verify at: https://github.com/dhruv-anand-aintech/agent-rules-sync/releases
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.
- 6d ago First seen · 297 lines · 3,509 tokens per session scan C f9edd972e82e
agent-rules-sync CLAUDE.md is an instructions file published in the GitHub repository dhruv-anand-aintech/agent-rules-sync (7 stars, last pushed 1mo ago), licensed MIT. It adds 3,509 tokens to every session, about $0.0175 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).