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.
npx agentmods add instructions/bahayonghang/my-ai-cli-toolkit/agents-mdgit clone --depth 1 https://github.com/bahayonghang/my-ai-cli-toolkitWrote 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/bahayonghang/my-ai-cli-toolkit/agents-md)<a href="https://agentmods.dev/instructions/bahayonghang/my-ai-cli-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/bahayonghang/my-ai-cli-toolkit/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 | $0.01093 | $0.01093 |
| Opus 5 | $0.00547 | $0.00547 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
my-ai-cli-toolkit 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 4d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
This AGENTS.md governs the repository root and all descendants unless a deeper AGENTS.md narrows the scope. Before broad search or repo-wide grep, read ./code_map.md and use its routing/search anchors to choose targeted files.
Project Structure & Module Organization
This repository organizes content at the repo root. Installable skills live under skills/<category>/<skill-name>/; platform-scoped commands/agents/prompts/rules sit under platforms/<platform>/; runtime hook assets for Claude Code are at platforms/claude/hooks/; shared validation scripts live in scripts/. Keep navigation/search detail in code_map.md, not in this file. Check scoped guidance files such as platforms/codex/AGENTS.md and platforms/claude/AGENTS.md before editing a nested area that provides its own instructions.
Build, Test, and Development Commands
Use just from the repository root:
just ci— full local CI:docs-check,skills-check,python-check,node-test, thengit diff --check.just lint—skills-check+python-check.just skills-check— runsscripts/check.pyoverskills/.just python-check— byte-compiles every*.pyunderskills/,platforms/, andscripts/(skipsscaffolds).just node-test— discovers and runs Node skill tests underskills/**/tests/*.mjs.
Coding Style & Naming Conventions
Follow existing language conventions instead of introducing local variants. Markdown should stay concise; use kebab-case for content directory names and skill slugs. Python scripts under skills/, platforms/, and scripts/ must remain byte-compilable (just python-check). Node skill scripts target plain Node >= 20 and live alongside their tests/*.mjs. Keep SKILL.md frontmatter in the documented top-level form: name, description, category, tags, version.
Testing Guidelines
Prefer targeted checks while iterating: just skills-check for metadata changes, just node-test for Node skill changes, and just python-check for Python edits. Run just ci once from the repository root before finishing or opening a PR. When adding or changing a Node skill, add or update a matching test file in its tests/ directory.
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.
- 4d ago First seen · 52 lines · 1,093 tokens per session scan A 2600f3271808
my-ai-cli-toolkit AGENTS.md is an instructions file published in the GitHub repository bahayonghang/my-ai-cli-toolkit (16 stars, last pushed yesterday), licensed MIT. It adds 1,093 tokens to every session, about $0.0055 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.