Borrowing it
Nothing to install: this file belongs to jellydn/my-ai-tools. 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/jellydn/my-ai-tools/main/AGENTS.mdgit clone --depth 1 https://github.com/jellydn/my-ai-toolsWrote 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/jellydn/my-ai-tools/agents-md)<a href="https://agentmods.dev/instructions/jellydn/my-ai-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/jellydn/my-ai-tools/agents-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.01628 | $0.01628 |
| Opus 5 | $0.00814 | $0.00814 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
my-ai-tools AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
What This Is
Monorepo for my-ai-tools — source-of-truth configs for 14+ AI coding assistants (Claude Code, OpenCode, Amp, Codex, Gemini, Antigravity, Cursor, Cline, Grok, etc.). It installs configs to ~/.claude/, ~/.config/opencode/, ~/.pi/, etc. and exports them back via generate.sh. Per-tool configs live in configs/<tool>/.
Essential Commands
bash -n cli.sh generate.sh lib/*.sh lib/install.sh # Syntax gate (CI runs this)
bash -n cli.sh generate.sh install.sh scripts/*.sh # CI gates this exact set
./cli.sh --dry-run # Preview install plan — ALWAYS run first
./cli.sh # Install configs into $HOME
./generate.sh --dry-run # Preview export
./generate.sh # Export local configs from $HOME back to repo
./scripts/sync-token-efficiency.sh --check # Verify profiles are in sync (exit 1 if stale)
biome check . # Format check (tabs, 120 width, double quotes)
biome check --write . # Format in place
bats tests/ # Run ALL functional tests locally
bats tests/cli.bats # Run a single test file
Workflow
./cli.sh --dry-run → git diff → ./cli.sh → git diff → commit
Never run ./cli.sh without --dry-run first. Config validation runs automatically and warns on failures.
cli.sh Flags
--dry-run— side-effect-free preview--backup/--no-backup— backup existing configs (auto-prompted interactively)-y/--yes— non-interactive; only processes your active tools. Auto-activated in CI/piped input. Triggers network installs of ~20 external CLIs before the core config copy.--migrate-gemini— one-step Gemini→Antigravity CLI migration--rollback— restore from the most recent$HOME/ai-tools-backup-{timestamp}-v/--verbose— verbose logging-h/--help— print usage options and exit
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 · 94 lines · 1,628 tokens per session scan A a6edb40cab54
my-ai-tools AGENTS.md is an instructions file published in the GitHub repository jellydn/my-ai-tools (119 stars, last pushed 3d ago), licensed MIT. It adds 1,628 tokens to every session, about $0.0081 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
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.