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 commands/mturac/everything-openai-codex/learngit clone --depth 1 https://github.com/mturac/everything-openai-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/commands/mturac/everything-openai-codex/learn)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/learn"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/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.00008 | $0.00331 |
| Opus 5 | $0.00004 | $0.00166 |
| Sonnet 5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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 today.
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 Command
Extract patterns, learnings, and reusable insights from the current session: $ARGUMENTS
Your Task
Analyze the conversation and code changes to extract:
- Patterns discovered - Recurring solutions or approaches
- Best practices applied - Techniques that worked well
- Mistakes to avoid - Issues encountered and solutions
- Reusable snippets - Code patterns worth saving
Output Format
Patterns Discovered
Pattern: [Name]
- Context: When to use this pattern
- Implementation: How to apply it
- Example: Code snippet
Best Practices Applied
- [Practice name]
- Why it works
- When to apply
Mistakes to Avoid
- [Mistake description]
- What went wrong
- How to prevent it
Suggested Skill Updates
If patterns are significant, suggest updates to:
skills/coding-standards/SKILL.mdskills/[domain]/SKILL.mdrules/[category].md
Instinct Format (for continuous-learning-v2)
{
"trigger": "[situation that triggers this learning]",
"action": "[what to do]",
"confidence": 0.7,
"source": "session-extraction",
"timestamp": "[ISO timestamp]"
}
TIP: Run /learn periodically during long sessions to capture insights before context compaction.
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.
- today First seen · 62 lines · 8 tokens per session scan A 4d46f77cd0c3
learn is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 10d ago), licensed MIT. It adds 8 tokens to every session and 331 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
selfloop
Start or control a persistent SIPS loop whose only objective is improving SIPS and the agent operating it through measured, verified iterations.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
patterns
Show the full agentpatterns report — success rate, approach→outcome correlation, top patterns.
verify
Spawn a fresh-context verifier subagent to check completed work against its specification before trusting it.