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 skills/othmanadi/apex/apex-learnnpx skills add OthmanAdi/APEX --skill apex-learngit clone --depth 1 https://github.com/OthmanAdi/APEXWrote 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/skills/othmanadi/apex/apex-learn)<a href="https://agentmods.dev/skills/othmanadi/apex/apex-learn"><img src="https://agentmods.dev/badge/skills/othmanadi/apex/apex-learn.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.00079 | $0.01012 |
| Opus 5 | $0.00039 | $0.00506 |
| Sonnet 5 | $0.00016 | $0.00202 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
apex-learn 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 5d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APEX Learn
Analyze what happened during a task, extract reusable knowledge, and persist it to AGENTS.md so the entire agent team improves over time.
When to Use
Run this skill in any of these situations:
- After completing a Tier 1, 2, or 3 task
- When the human corrected you on the same issue twice (two-strike rule)
- When you discovered a non-obvious pattern or convention
- When a task took significantly longer than expected
- When the human explicitly asks to update the rules
The Two-Strike Rule
This is the core mechanism. If you are corrected on the same type of issue twice:
- First correction — Fix the issue, note it mentally
- Second correction — Fix the issue AND run
apex-learnto add a permanent rule
This prevents the same mistake from recurring across sessions.
Workflow
- Identify friction points
- Classify the learning
- Draft the rule
- Append to AGENTS.md
- Verify the update
Step 1: Identify Friction Points
Ask yourself these questions about the completed task:
## Friction Analysis
1. Where did I get stuck or make mistakes?
2. What did the human correct me on?
3. What took longer than expected and why?
4. What assumptions did I make that were wrong?
5. What patterns did I discover that aren't documented?
Step 2: Classify the Learning
Each learning falls into one of these categories:
| Category | Example | Where it Goes in AGENTS.md |
|---|---|---|
| Code style | "Always use named exports" | ## Code Style section |
| Architecture | "Services never call controllers" | ## Architecture Rules section |
| Workflow | "Always run tests before committing" | ## Workflow section |
| Boundaries | "Never modify the auth module" | ## Boundaries section |
| Preferences | "Prefer descriptive over short names" | ## Preferences section |
| Tool usage | "Use pnpm, not npm" | ## Tools section |
Step 3: Draft the Rule
Write the rule in imperative form. Be specific and actionable:
What ships with it
3 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.
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.
- 5d ago First seen · 134 lines · 79 tokens per session scan A 837e8a4e1267
apex-learn is a skill published in the GitHub repository OthmanAdi/APEX (2 stars, last pushed 5mo ago), licensed MIT. It adds 79 tokens to every session and 1,012 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…