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/pathakcodes/learnfromclaude/settingsgit clone --depth 1 https://github.com/pathakcodes/learnFromClaudeWhat 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.00011 | $0.00155 |
| Opus 5 | $0.00005 | $0.00077 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
settings 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 yesterday.
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
Open the user's learnFromClaude CONFIG.md so they can tweak what cards get extracted and how many.
- If the dashboard is already running, the easiest path is pressing
,in the UI — it opens the settings modal. Tell the user that first. - Otherwise, open
~/.claude/learnFromClaude/CONFIG.mdin their editor with the Read tool so they can review the current values (cards_per_session, min/max session events, extraction categories, skip rules, card style, custom instructions). - If they want to edit specific knobs, make the targeted changes with Edit. The summarizer picks up changes at the next session end — no restart needed.
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.
- yesterday First seen · 10 lines · 11 tokens per session scan A 4af4868f1220
settings is a command published in the GitHub repository pathakcodes/learnFromClaude (2 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 155 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.
Other commands, from other repositories
autobot
Launch a bot command in an isolated autobot session with its own worktree, backend, and frontend.
fixbot
You are the orchestrator for the fixbot workflow. Fixbot fixes a Linear issue, running directly in this project against the locally running server. For an isolated worktree version, use /autobot /fixbot instead.
qabot-report
Regenerate the QA report from existing review files.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.