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/apiksdev/axel-core/claude-mdgit clone --depth 1 https://github.com/apiksdev/axel-coreWhat 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.00467 | $0.00467 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
axel-plugin 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
AXEL Plugin
<document type="project">
<enforcement>
<![CDATA[
⛔ CONTENT DUPLICATION RULES
- ❌ NEVER copy content from referenced documents into new documents
- Referenced documents are already loaded via context or on-demand loading
- New documents should only contain unique, non-duplicated information
- Reference existing content via <read src=".."/> in <documents> block
- If content exists elsewhere → reference it, do not duplicate it
⛔ XML COMMENT FORMAT RULES
- ❌ NEVER use multi-line decorative comments
- ❌ NEVER use box-style comments with separator lines (====, ----, ****)
- ❌ NEVER use comments like: <!-- ========== SECTION ========== -->
- ✅ ALWAYS use single-line format: <!-- stage_id: Description -->
- Comment must be placed directly before the element it describes
]]>
</enforcement>
<project name="axel-plugin" version="1.0.1">
<description>
AXEL (AI XML Execution Language) development environment for creating and testing
structured AI behavior components. AXEL is an XML-based DSL plugin for Claude Code
that addresses inconsistent AI behavior through enforceable instructions that persist
across sessions. This project serves as the development workspace for building AXEL
components including Skills (specialized AI expertise), Agents (autonomous task executors),
Workflows (multi-step processes), Commands (slash command definitions), Todos (task management),
and Memory systems (cross-session context persistence).
</description>
<stack>
- language: XML, Markdown, YAML
- platform: Claude Code
- type: DSL (Domain-Specific Language)
</stack>
</project>
<locale default="en">
- code: en
- docs: en
- communication: tr
- commits: en
- todos: tr
</locale>
<understanding/>
</document>
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 · 60 lines · 467 tokens per session scan A a7449569cd65
axel-plugin is an instructions file published in the GitHub repository apiksdev/axel-core (7 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 467 tokens to every session, about $0.0023 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.
buildNext
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
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
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.