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.
git clone --depth 1 https://github.com/pathakcodes/learnFromClaudeWrote 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/pathakcodes/learnfromclaude/settings)<a href="https://agentmods.dev/commands/pathakcodes/learnfromclaude/settings"><img src="https://agentmods.dev/badge/commands/pathakcodes/learnfromclaude/settings/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/commands/pathakcodes/learnfromclaude/settings"><img src="https://agentmods.dev/badge/commands/pathakcodes/learnfromclaude/settings.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.00155 |
| Opus 5.5 | $0.00004 | $0.00062 |
| Sonnet 5.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 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
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.
- 1mo ago 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 6mo ago), licensed MIT. It adds 11 tokens to every session and 155 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-images:validate-config
Validate wrangler.jsonc configuration, verify Cloudflare Images bindings, check environment variables, and test Workers integration. Ensures correct setup for using Cloudflare Images with Cloudflare Workers.
cloudflare-queues:setup
Interactive wizard to set up Cloudflare Queues with queue creation, producer/consumer binding configuration, and Dead Letter Queue setup. Use when user wants to create first queue or add queues to existing Worker.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.