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 skills add nortonx/ai-tooling-free --skill learngit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/skills/nortonx/ai-tooling-free/learn)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/learn"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/learn/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/skills/nortonx/ai-tooling-free/learn"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/learn.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.00015 | $0.00217 |
| Opus 5 | $0.00008 | $0.00109 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 8d 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
Arguments
<concept>
- Required. The concept, term, or technology you want explained — free-text.
- Examples:
/learn user story,/learn Wilson score interval,/learn closure in JavaScript
Copilot CLI note:
$ARGUMENTSdoesn't substitute in skills — include the argument inline in your prompt.
Help me understand: $ARGUMENTS
Explain using:
- Simple explanation (ELI5)
- Technical explanation
- Real-world analogy
- Code example
- Common pitfalls
- Best practices
- Related concepts
- Resources for deeper learning
Connect to concepts I already know.
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.
- 8d ago First seen · 34 lines · 15 tokens per session scan A de2819a522aa
learn is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 24d ago), licensed MIT. It adds 15 tokens to every session and 217 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 skills, from other repositories
code-tour
Use when a user asks for a code tour, onboarding walkthrough, architecture tour, or PR tour — creates persona-targeted, step-by-step .tour files with real file and line anchors.
eli5
Explain the subject already in context using simple, respectful language, a familiar analogy, the proper grown-up terms, and the point where the analogy stops matching reality. Use when the user says "explain like I'm five", "explain it to me like I'm 5", "ELI5", "explain this simply", "make this easy to understand"…
manim-video
Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
drupal-mental-model
Use when explaining code, debugging, or discussing architecture with Jack — map programming concepts to Drupal equivalents he already knows from years of Drupal/theming work. Triggers on code reviews, debugging walkthroughs, architecture discussions, inline code explanations, or whenever a non-Drupal framework concept…
onboard
Walk a new teammate through the team's curated agent toolchain.
docs-sync
Keep project documentation in sync with code changes. Identifies which docs need updating after a PR merges or code changes, drafts the updates, and manages doc site structure (mkdocs, docusaurus, vitepress). Use when: (1) a PR just merged and docs may need updating, (2) the user says "update the docs" or "sync docs"…