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/vthinkdeveloper/vthink-agent-toolkit/claude-mdgit clone --depth 1 https://github.com/vthinkdeveloper/vthink-agent-toolkitWhat 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.00433 | $0.00433 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
vthink-agent-toolkit 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 yesterday.
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
CLAUDE.md — vthink-agent-toolkit
This file provides Claude Code with context about this repository. For agent-runtime-agnostic instructions, see AGENTS.md.
What This Repo Is
vthink-agent-toolkit is a collection of agent-agnostic skills, agents, and workflows. Claude Code is one supported runtime — not the assumed one. Claude Code-specific assets (hooks, MCP configs, settings templates, rules) live in platforms/claude-code/.
Directory Structure
skills/<name>/SKILL.md # Skills — portable across all runtimes
agents/<name>/AGENT.md # Agents — portable across all runtimes
playbooks/ # Recipes for combining skills and agents
platforms/claude-code/ # Claude Code-specific assets
hooks/ # Pre/post-tool shell scripts
mcp/ # MCP server config snippets
settings-templates/ # .claude/settings.json starters
rules/ # CLAUDE.md snippets
.claude/commands/ # Slash commands (Claude Code)
output-styles/ # Response style files (tone, structure, formatting)
templates/ # Starter templates for contributors
Tour
If a user says "I'd like a tour", install the setup wizard and invoke it:
mkdir -p ~/.claude/agents
cp agents/setup-wizard/AGENT.md ~/.claude/agents/setup-wizard.md
Then invoke the setup-wizard agent.
When Helping a Contributor Add Something New
- Read
CONTRIBUTING.md - Use the right template from
templates/ - Frontmatter must have only
nameanddescription— nothing else - Skills go in
skills/<name>/SKILL.md, agents inagents/<name>/AGENT.md - Claude Code-specific contributions go in
platforms/claude-code/ - Update
CATALOG.md— mandatory, reviewers check this
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.
- yesterday First seen · 44 lines · 433 tokens per session scan A 7e78102e09d0
vthink-agent-toolkit CLAUDE.md is an instructions file published in the GitHub repository vthinkdeveloper/vthink-agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 433 tokens to every session, about $0.0022 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
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).
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.
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).
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.
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.