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/liortesta/clawdagent/learn-mistakegit clone --depth 1 https://github.com/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/learn-mistake)<a href="https://agentmods.dev/commands/liortesta/clawdagent/learn-mistake"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/learn-mistake.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.00000 | $0.00335 |
| Opus 5 | $0.00000 | $0.00168 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
learn-mistake 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 4d 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 From Mistake
The user is telling you about a mistake you just made. This is a learning opportunity.
Process:
- Acknowledge the specific mistake — be precise about what went wrong
- Explain WHY it was wrong — root cause, not just symptoms
- Propose a rule to prevent recurrence — specific and actionable
- Add the rule to CLAUDE.md under "Self-Correction Rules (LEARNED)" section with today's date
- Check if a hook can enforce it — if the mistake is about code patterns, consider adding a PostToolUse hook that catches it automatically
Rule Format in CLAUDE.md:
- [DATE] RULE: [specific, actionable rule]
CONTEXT: [what happened that triggered this rule]
Examples:
[2025-01-15] RULE: Always use pnpm, never npm, in this project. CONTEXT: Used npm install which created package-lock.json conflict.[2025-01-16] RULE: API routes go in src/app/api/, not src/routes/. CONTEXT: Created route in wrong directory, 404 error.[2025-01-17] RULE: Always run tests before committing, even for "trivial" changes. CONTEXT: One-line fix broke 3 tests.
Rules:
- NEVER be defensive — own the mistake
- ALWAYS make the rule specific enough to be actionable
- ALWAYS verify the rule is added to CLAUDE.md before completing
Mistake: $ARGUMENTS
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.
- 4d ago First seen · 29 lines · 0 tokens per session scan A b93a15e1d0a5
learn-mistake is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 335 tokens. 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.