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/artusjs/artusx/claude-mdgit clone --depth 1 https://github.com/artusjs/artusxWrote 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/artusjs/artusx/claude-md)<a href="https://agentmods.dev/instructions/artusjs/artusx/claude-md"><img src="https://agentmods.dev/badge/instructions/artusjs/artusx/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.01606 | $0.01606 |
| Opus 5 | $0.00803 | $0.00803 |
| Sonnet 5 | $0.00321 | $0.00321 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
artusx 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 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Available Skills
artusx-best-practices
A Claude Code skill is available at skills/artusx-best-practices/ to assist with ArtusX application development. This skill provides:
- Plugin Development: Complete patterns for creating ArtusX plugins with lifecycle hooks
- Decorators: Usage examples for @Controller, @Middleware, @Inject, HTTP route decorators
- Testing: Setup patterns with ArtusScanner, ArtusApplication, and Jest
- Common Tasks: Step-by-step guides for controllers, middleware, database integration
- Troubleshooting: Solutions for lifecycle issues, DI failures, configuration errors
The skill automatically activates when working with:
- Creating or modifying ArtusX plugins
- Implementing controllers and middleware
- Setting up tests for ArtusX packages
- Debugging lifecycle hook issues
- Configuring decorators and dependency injection
For detailed reference, see the skill's reference files in skills/artusx-best-practices/references/.
Project Overview
ArtusX is an ecosystem based on Artus.js framework (https://www.artusjs.org), managed as a Rush.js monorepo. It provides a plugin-based architecture for building web applications with support for multiple frameworks (Koa, Express, Nest).
Development Commands
Environment Setup
# Install Rush.js globally (required)
npm install -g @microsoft/rush
# Install all dependencies
rush update
# Rebuild all packages
rush rebuild
Building and Testing
# Build specific package
rush build -t <package-name>
# Rebuild specific package (clean build)
rush rebuild -t <package-name>
# Run tests for a specific package (from package directory)
cd packages/plugins/koa
rushx test
# Run tests with coverage
rushx cov
# Run linting
rushx lint
rushx lint:fix
Running Applications
# Development mode (from app directory)
cd packages/apps/artusx-koa
rushx dev
# Production mode
rushx start
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 · 229 lines · 1,606 tokens per session scan A 92d76ee557cc
artusx CLAUDE.md is an instructions file published in the GitHub repository artusjs/artusx (11 stars, last pushed 2mo ago), licensed MIT. It adds 1,606 tokens to every session, about $0.0080 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.