A router for choosing relevant local AI-tooling context and producing compact machine-readable instructions. It uses defined catalogs, policies, and workspace metadata.

Use it to discover workspace context, select routing rules, and generate structured APEXlang outputs.

It reduces guesswork about which local information is authoritative and what context an AI tool should load.

apexlang — Skill for Claude Code and Codex by maxime-tremblay

Install

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.

Any agent

npx skills add maxime-tremblay/APEXLang-Project-Template --skill apexlang

Clone the repo

git clone --depth 1 https://github.com/maxime-tremblay/APEXLang-Project-Template

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/maxime-tremblay/apexlang-project-template/apexlang/github.svg)](https://agentmods.dev/skills/maxime-tremblay/apexlang-project-template/apexlang)

Your own site

<a href="https://agentmods.dev/skills/maxime-tremblay/apexlang-project-template/apexlang"><img src="https://agentmods.dev/badge/skills/maxime-tremblay/apexlang-project-template/apexlang/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/maxime-tremblay/apexlang-project-template/apexlang"><img src="https://agentmods.dev/badge/skills/maxime-tremblay/apexlang-project-template/apexlang.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,241 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00020	$0.02241
Opus 5	$0.00010	$0.01120
Sonnet 5	$0.00004	$0.00448
Haiku 4.5	$0.00002	$0.00224

Measured 10d ago against content hash 11fa649c42ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

apexlang 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 10d 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.

.claude/skills/apex/apexlang/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill — APEXlang

SKILL.md is the north-star source of truth and main routing entry point for packaged APEXlang generation. Read compact JSON assets before broader prose.

Start Order

assets/routing-catalog-main.json
assets/routing-load-policy.json
assets/apexlang/domains-catalog.json
assets/workspace-intelligence.json
Run node tools/apexctl.mjs workspace probe from the packaged skill root.
The temp-runtime context-resolution.json report under APEXLANG_OUTPUT_ROOT, when present

Only the package-root asset names above are valid for the public package. Do not substitute legacy router or load-policy aliases from copied prompts.

Local Context Contract

Discovery boundary is the current local AI tooling session directory only.
Prefer authoritative offline context from metadata definitions, data models, or API contracts.
Treat specs/ and requirements/ as hints and disambiguation only.
Do not infer schema or API shape from prose, names, or headings.
Treat artifacts/ as optional runtime output only. Do not require it before generation starts and do not use it as source context.
Treat any apex-exports path segment as backup/export material only. Ignore it for app resolution, metadata discovery, bounded scans, template/source selection, and generation unless the user explicitly asks for read-only export inspection, migration, or recovery analysis.
All node tools/apexctl.mjs ... commands are package-root relative: run them from the packaged skill root, or invoke that script by explicit path.
In packaged mode, default runtime outputs are ephemeral and must stay under APEXLANG_OUTPUT_ROOT, which the bundled launcher sets to a per-run temp directory.
When app or page scope appears with translation, localization, target-language, messages.apx, or APP_TEXT$ wording, route first to the shared-components translation guidance before generic page/app generation references.
Plain app/page localization requests must be satisfied by text-message conversion plus &APP_TEXT$... consumption rewiring. Do not satisfy them by inserting direct translated literals into component attributes.

Read the full file on GitHub · 76 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

10d ago First seen · 76 lines · 20 tokens per session scan A 11fa649c42ca

Subscribe to this mod's changes

apexlang is a skill published in the GitHub repository maxime-tremblay/APEXLang-Project-Template (2 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 2,241 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.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens