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 agents/apiksdev/axel-core/axel-agent-template-bootstrapgit 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.00015 | $0.00322 |
| Opus 5 | $0.00008 | $0.00161 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
agent-template-bootstrap 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 2d 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.
What it actually says
AXEL Template: Agent
<document type="reference">
<enforcement>
<![CDATA[
- Read `src` attribute from <read/> elements to locate sub-templates
- ${CLAUDE_PLUGIN_ROOT} resolves to plugin installation directory
- load="on-demand" means template loads when user request matches ask keywords
- Select appropriate sub-template based on execution pattern needed
]]>
</enforcement>
<objective>
Navigation template for agent execution pattern selection.
Two patterns: Linear (no stages) and Staged (with stages, branching, parallel, loop).
</objective>
<templates load="on-demand">
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/templates/agents/refs/AXEL-Agent-Linear-Tpl.md"
ask="[simple, linear, basic, straightforward, no stages]"/>
<read src="${CLAUDE_PLUGIN_ROOT}/skills/skill-axel-core/templates/agents/refs/AXEL-Agent-Staged-Tpl.md"
ask="[staged, complex, branching, parallel, loop, retry, orchestration]"/>
<understanding>
Linear template: Simple agents without stages, text-based execution.
Staged template: Complex agents with stages, branching, parallel, loops.
</understanding>
</templates>
<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.
- 2d ago First seen · 41 lines · 15 tokens per session scan A eace0f94f968
agent-template-bootstrap is an agent published in the GitHub repository apiksdev/axel-core (7 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 322 once invoked, about $0.0001 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
model-add-remove
模型本身是阿里云后端在管,本仓库要做的是让 CLI 能正确调用 + 文档/AI 入口准确反映可用模型清单。.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…