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/notque/vexjoy-agent/claude-mdgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/claude-md)<a href="https://agentmods.dev/instructions/notque/vexjoy-agent/claude-md"><img src="https://agentmods.dev/badge/instructions/notque/vexjoy-agent/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 | $0.00859 | $0.00859 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
vexjoy-agent 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VexJoy Agent
How This Toolkit Works
The toolkit uses agents, skills, hooks, and scripts to absorb complexity that would otherwise fall on the user. Behavioral enforcement lives in these mechanisms, not in this file.
Route to agents. The main thread is an orchestrator. It classifies requests, dispatches agents, and evaluates results. It delegates source code reading, file edits, and analysis to specialized agents. Dispatch an agent for all work. The main thread orchestrates, agents execute.
Load only what you need. Context is a scarce resource. Agents carry domain knowledge, skills carry methodology, and reference files carry deep content, all loaded on demand. Load only the context required for the current task.
LLMs orchestrate, programs execute. If a process is deterministic and measurable (file searching, test execution, build validation, frontmatter checking), use a script. Reserve LLM judgment for contextual diagnosis, design decisions, and code review.
Write dense. High fidelity, minimum words. Prefer tables and lists over paragraphs. See the Communication Standard below.
Communication Standard
The Dense-Complete Writing standard is the structural guide for everything we do. It governs every generated text: replies to the user, plain text, skill and instruction files, and code comments.
- Shortest accurate word; never a long word where a short one serves.
- Cut every word that carries no instruction, rule, or decision.
- Plain English, not jargon.
- Concrete over abstract.
- Put heavy qualifications in separate short sentences.
- Completeness: treat content as fixed and wording as negotiable: carry every required point through the draft, then choose the shortest plain words that say those points exactly.
Test: say everything the task needs, and not one word more. Full rules and scope: skills/shared-patterns/dense-complete-writing.md.
The Google Developer Documentation Style standard applies alongside it, by precedence, highest first:
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 Changed · -17 tokens per session 50333242a381
- 5d ago First seen · 56 lines · 876 tokens per session scan A 547c1307e617
vexjoy-agent CLAUDE.md is an instructions file published in the GitHub repository notque/vexjoy-agent (420 stars, last pushed today), licensed MIT. It adds 859 tokens to every session, about $0.0043 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
context-to-action-skills AGENTS.md
Instructions for tmusser/context-to-action-skills, covering agents, repo model, safety rules, output rules and validation commands.
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.
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.