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/samibs/skillfoundry/learngit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/learn)<a href="https://agentmods.dev/commands/samibs/skillfoundry/learn"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/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.00000 | $0.01765 |
| Opus 5 | $0.00000 | $0.00882 |
| Sonnet 5 | $0.00000 | $0.00353 |
| Haiku 4.5 | $0.00000 | $0.00177 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Powered Development & Learning Guide
A consolidated reference combining advanced Claude Code workflows and AI-assisted learning techniques.
Persona: See agents/ai-workflows-and-learning-guide.md for full persona definition.
Hard Rules
- ALWAYS validate code examples before presenting them to learners
- NEVER include hardcoded credentials or insecure patterns in examples
- REJECT learning paths that skip error handling fundamentals
- DO verify that security best practices are included in every workflow
- CHECK that examples handle edge cases and demonstrate proper validation
- ENSURE all code samples include error handling and input validation
- IMPLEMENT progressive complexity — start simple, add security and error handling early
Part 1: Claude Code Workflow for 2026
Based on RAmjad's video "My Claude Code Workflow for 2026" (16k views) — summarized by Om Nalinde
"This dude from Cambridge plays with Claude Code like he owns it."
1. Video-Based Specification (Spec Phase)
Screen Recording
Instead of writing a spec from scratch, find an existing product similar to your idea. Record your screen while using it and talking through your specific feature ideas and changes.
Generate PRD
Upload this video to Gemini 1.5 Pro (or Gemini 3 Pro/Free Pro) and ask it to generate a Product Requirement Document (PRD).
Refine Spec
Use the "Ask User Question" tool in Claude Code. Prompt it to interview you about the generated spec to fill in missing details (e.g., "How should the emoji picker be positioned?").
Package Discovery
Feed the refined spec into ChatGPT with "Heavy Thinking" (likely OpenAI's o1/o3 models) to search for and recommend specific, well-maintained GitHub packages (e.g., for a WYSIWYG editor) to avoid building complex components from scratch.
2. The Orchestrator Role
Design Feedback Loops
Your primary job is not to write code but to design loops where the agent can build, fail, and learn.
Monitor & Update
Watch the agent's reasoning. If it makes a mistake, don't just fix the code—update the claude.md (project instructions file) to prevent that specific mistake from happening again.
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 · 233 lines · 0 tokens per session scan A 553e2d45c723
learn is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,765 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-09-03.
Other commands, from other repositories
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.