Borrowing it
Nothing to install: this file belongs to artivilla/agents-config. 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/artivilla/agents-config/main/CLAUDE.mdgit clone --depth 1 https://github.com/artivilla/agents-configWrote 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/artivilla/agents-config/claude-md)<a href="https://agentmods.dev/instructions/artivilla/agents-config/claude-md"><img src="https://agentmods.dev/badge/instructions/artivilla/agents-config/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.00374 | $0.00374 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
agents-config 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 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.
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
agent config
Personal agent setting settings, skills, agents, and rules, synced across machines via symlinks.
Commands
./install.sh # Set up symlinks (run after cloning)
./install.sh --dry-run # Preview what would be done
./sync.sh # Show sync status
./sync.sh add <type> <name> # Add a local item to repo
./sync.sh remove <type> <name> # Remove item from repo (keeps local)
./sync.sh pull # Pull latest and reinstall symlinks
./sync.sh push # Commit and push changes
./sync.sh undo # Restore from last backup
./sync.sh validate # Validate all skills
./sync.sh backups # List available backups
bats tests/ # Run tests
Types: skill, agent, rule
Testing
Tests use Bats. Run bats tests/ to execute all tests. Tests run in isolated temp directories.
See .claude/rules/testing.md for testing conventions.
Key Files
install.sh- Creates symlinks from ~/.claude (and other agents) to this reposync.sh- Manages syncing items between local and repolib.sh- Shared functions (config parser) used by both scriptsagents.conf- Config file listing which agents to install skills totests/- Bats test suite
For detailed workflows, see .claude/rules/workflows.md.
Verification
After making changes:
bats tests/- Run all tests./sync.sh validate- Validate all skills
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 · 44 lines · 374 tokens per session scan A ccd87f303da6
agents-config CLAUDE.md is an instructions file published in the GitHub repository artivilla/agents-config (0 stars, last pushed 2mo ago), licensed MIT. It adds 374 tokens to every session, about $0.0019 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 instructions, from other repositories
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).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.