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 skills add Luohaothu/everything-codex --skill learngit clone --depth 1 https://github.com/Luohaothu/everything-codexWrote 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/luohaothu/everything-codex/learn)<a href="https://agentmods.dev/skills/luohaothu/everything-codex/learn"><img src="https://agentmods.dev/badge/skills/luohaothu/everything-codex/learn/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.
<a href="https://agentmods.dev/skills/luohaothu/everything-codex/learn"><img src="https://agentmods.dev/badge/skills/luohaothu/everything-codex/learn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 23 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00018 | $0.00348 |
| Opus 5.5 | $0.00007 | $0.00139 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
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 1mo 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
Learn Skill
Analyze the current session and extract patterns worth saving as reusable skills.
When to Use
Run /learn when you've solved a non-trivial problem during a session.
What to Extract
- Error Resolution Patterns — What error, root cause, and fix?
- Debugging Techniques — Non-obvious steps, tool combinations
- Workarounds — Library quirks, API limitations, version-specific fixes
- Project-Specific Patterns — Codebase conventions, architecture decisions
Output Format
Create a skill file at ~/.codex/skills/learned/<pattern-name>/SKILL.md:
---
name: <pattern-name>
description: <what this pattern solves>
---
# <Descriptive Pattern Name>
**Extracted:** <Date>
**Context:** <When this applies>
## Problem
<What problem this solves>
## Solution
<The pattern/technique/workaround>
## Example
<Code example if applicable>
## When to Use
<Trigger conditions>
Process
- Review the session for extractable patterns
- Identify the most valuable/reusable insight
- Draft the skill file
- Ask user to confirm before saving
- Save to
~/.codex/skills/learned/
Guidelines
- Don't extract trivial fixes (typos, simple syntax errors)
- Don't extract one-time issues (specific API outages)
- Focus on patterns that save time in future sessions
- Keep skills focused — one pattern per skill
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.
- 1mo ago First seen · 63 lines · 18 tokens per session scan A 2c16d6aba66f
learn is a skill published in the GitHub repository Luohaothu/everything-codex (25 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 348 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
self-improve-with-tinyfish
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
flashcards
Spaced repetition flashcard system for learning. SM-2 algorithm, supports text and cloze deletion cards.
flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
curate
Adds developer-authored annotations to the gauntlet knowledge base. Use when capturing tribal knowledge or rationale not visible in code.