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 firatcand/forge --skill learngit clone --depth 1 https://github.com/firatcand/forgeWrote 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/firatcand/forge/learn)<a href="https://agentmods.dev/skills/firatcand/forge/learn"><img src="https://agentmods.dev/badge/skills/firatcand/forge/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/firatcand/forge/learn"><img src="https://agentmods.dev/badge/skills/firatcand/forge/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.00028 | $0.01046 |
| Opus 5.5 | $0.00011 | $0.00418 |
| Sonnet 5.5 | $0.00006 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00105 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/learn
Delegate to learning-curator.
Triggers (any one makes the task "notable")
- Investigation took > 30 min
-
2 fix attempts before success
- Surprised by behaviour
- Found a non-obvious gotcha
- Made a non-trivial trade-off
- Bootstrapped something new (test framework, CI, infrastructure)
Process
-
Read the last commit + PR description + investigation file (if exists).
-
Extract:
- What we expected
- What actually happened
- Why
- What we'd do differently
-
Tag with relevant types.
-
Resolve the canonical learnings path.
docs/learnings/is gitignored (forge-dogfood publish-hygiene rule), so its single source of truth is the main checkout'sdocs/learnings/tree — not the working directory./pickup-taskhydrates worktrees bycp -rfrom the main checkout (skills/pickup-task/SKILL.mdlines 47–53), and/learnmust mirror that contract on the write side. Seespec/SPEC.md §Learnings storefor the canonical-store rule and why.Resolve the main checkout's absolute path via
git rev-parse --git-common-dir(which always resolves to the main checkout's.gitfrom anywhere — main or worktree). Compare againstpwd -Pso symlinked paths (e.g. macOS/var↔/private/var) don't trigger a spurious double-write:GIT_COMMON_DIR="$(git rev-parse --git-common-dir)" MAIN_ROOT="$(cd "$(dirname "${GIT_COMMON_DIR}")" && pwd -P)" PWD_REAL="$(pwd -P)" QUARTER="2026-Q2" # or current quarter, e.g. "$(date -u +%Y)-Q$((($(date -u +%m)-1)/3+1))" SLUG="kebab-case-slug-from-title" mkdir -p "${MAIN_ROOT}/docs/learnings/${QUARTER}" -
Refuse on collision. If
${MAIN_ROOT}/docs/learnings/${QUARTER}/${SLUG}.mdalready exists, stop and surface the conflict — pick a different slug, orEditthe existing learning instead of writing a new one. Do not silently overwrite a prior learning. -
Write the canonical record first to the main checkout's absolute path using the
Writetool. This is the load-bearing write; do not skip it even on errors elsewhere:
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 · 112 lines · 28 tokens per session scan A d4c515bae789
learn is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,046 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
design
Set visual and interaction direction for any UI surface (web, React, TUI, CLI, desktop, Qt, design-system tokens) before any UI code. Direction-first: generates 3-4 distinct directions via verbalized sampling, picks one via per-axis single-select, then derives palette, typography, spacing, motion budget. Loads when…
askme
Verbalized Sampling (VS) protocol for intent exploration before planning, mode-aware. Default exhaustive runs full VS; collaborative runs tip-sharing dialogue; adversarial walks the design tree one fork at a time. Auto-detects from phrasing ("help me refine" → collaborative, "poke holes" → adversarial); override via…
grill-me
Adversarial relentless interview against any plan or design until shared understanding is reached. Walk the decision tree, resolve dependencies one answer at a time, recommend a default per question. Trigger when the user says "grill me", "stress-test this", "interview me about this design", or otherwise asks for…
fix
Polymorphic iterative repair loop — accept a verifier failure, structured findings (review/resolve/triage-issue), or a bug description; modify→verify→keep on green, auto-revert on guard regression, until clean or iteration cap. Use when the user says "fix", "make it pass", or "apply the findings", or hands an artifact…
git-branchless
Enforce idiomatic git-branchless during planning and executing tasks — detached-HEAD-first work, in-memory rebase via git move, event-log recovery via git undo, deferred branch creation, speculative-merge git sync for base updates. Use when planning or executing multi-commit work, history rewrites, stack edits…