Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ForgeyClap/claude-forgenpx agentmods add skills/forgeyclap/claude-forge/forge-deeplearnWrote 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/forgeyclap/claude-forge/forge-deeplearn)<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-deeplearn"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-deeplearn/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/forgeyclap/claude-forge/forge-deeplearn"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-deeplearn.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.00047 | $0.00875 |
| Opus 5.5 | $0.00019 | $0.00350 |
| Sonnet 5.5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
forge-deeplearn 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 20d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Learn Mode (WP2 — full-codebase priming scan)
Deep Learn Mode is an on-demand, read-only scan of the current project (.claude/forge-bin/forge-deeplearn.cjs) that produces an honest project-summary and risk-list BEFORE the Lead commits to a PRD or a big architectural change. It never writes into the scanned tree — its only output is its own artifact under .claude/ (with --store) and optional dashboard events.
When the Lead runs it
- A new or unfamiliar project (first
/forgerun, or "gebruik forge voor dit project" on a folder with no memory yet). - Before generating a PRD or acceptance criteria for a non-trivial feature.
- Before a large refactor, migration, or architecture change.
- Not needed for a 1-2 line fix, or a project already scanned this session — check
.claude/forge-artifacts/index.jsonlfirst.
How
node .claude/forge-bin/forge-deeplearn.cjs --path . --run <run_id> --store
--path <dir>— defaults to the current directory.--run <run_id>— logsdeep_learn_started/deep_learn_completedto that run's dashboard events (omit to run standalone).--store— persists the full result viaforge-store.cjs(.claude/forge-artifacts/deeplearn-<epoch>.json).
What it outputs
Stack (node/python/go/rust/dotnet/php/static + framework hints from package.json deps), file counts by category, likely entry points, tests presence, the 5 largest code files, and a risk-list (high/med/low) covering missing tests, oversized files (>800 lines), a missing README, TODO/FIXME density, secret-looking strings, and an unignored .env. Feed the summary + risks straight into the PRD's acceptance criteria, and hand any high risk to the Security Boss / security-reviewer; a secret-looking hit under a test/fixture/docs location (test/, tests/, __tests__/, test-evidence/, fixtures/, docs/, *.test.*, *.spec.*, *.md) is instead reported as a med secret-pattern-fixture-looking risk with a note pointing at forge-doctor.cjs's leak scan (forge-secret-scrub.cjs) as the real authority.
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.
- 20d ago Changed 3b1c22fa4a7d
- 25d ago Changed 6577ef221e24
- 1mo ago First seen · 34 lines · 47 tokens per session scan A 6447d9821e26
forge-deeplearn is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 21d ago), licensed MIT. It adds 47 tokens to every session and 875 once invoked, about $0.0002 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 skills, from other repositories
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
trailhead-view
Skill "trailhead-view" from ToRvaLDz/trailhead, covering load first, in order, routing: verb to engine, render the map: map [map], 🎯 destination and 🗒️ notes.
review
Use when operating as the Fabrik Review stage agent. This skill guides code review of an implementation, finding and fixing issues, and ensuring the PR is ready for human review.
implement-comment
Use when operating as the Fabrik Implement comment reviewer. This skill guides applying user-requested code changes during implementation, committing and pushing, and updating the task checklist — without signaling stage completion.
specify
Use when operating as the Fabrik Specify stage agent. This skill guides the specification and clarification of a feature request, turning a rough backlog issue into a clear, unambiguous spec before technical research begins.