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 skills/n4m3z/forge-core/forgeskillnpx skills add N4M3Z/forge-core --skill forgeskillgit clone --depth 1 https://github.com/N4M3Z/forge-coreWrote 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/n4m3z/forge-core/forgeskill)<a href="https://agentmods.dev/skills/n4m3z/forge-core/forgeskill"><img src="https://agentmods.dev/badge/skills/n4m3z/forge-core/forgeskill.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.00078 | $0.01235 |
| Opus 5 | $0.00039 | $0.00617 |
| Sonnet 5 | $0.00016 | $0.00247 |
| Haiku 4.5 | $0.00008 | $0.00123 |
Grade A, and why
ForgeSkill 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 3d 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.
The source is not reproduced here
Licensed EUPL-1.2
The repository is licensed EUPL-1.2, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
47 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .provenance/DescriptionOptimization.md.yaml 1.5 KB
- .provenance/EvalLoop.md.yaml 1.5 KB
- .provenance/SKILL.yaml 1.5 KB
- agents/.provenance/analyzer.md.yaml 1.5 KB
- agents/.provenance/comparator.md.yaml 1.5 KB
- agents/.provenance/grader.md.yaml 1.5 KB
- agents/analyzer.md 10 KB
- agents/comparator.md 7.1 KB
- agents/grader.md 8.8 KB
- assets/.provenance/eval_review.html.yaml 1.5 KB
- assets/eval_review.html 6.9 KB
- ClaudeSkill.md 3.4 KB
- CliToolIntegration.md 340 B
- CreateWorkflow.md 3.0 KB
- DescriptionOptimization.md 3.3 KB
- DynamicContextInjection.md 3.7 KB
- eval-viewer/.provenance/generate_review.py.yaml 1.5 KB
- eval-viewer/.provenance/viewer.html.yaml 1.5 KB
- eval-viewer/generate_review.py 16 KB runs code
- eval-viewer/viewer.html 44 KB
- EvalLoop.md 7.1 KB
- MultiProviderRouting.md 619 B
- PlatformAgnostic.md 1.1 KB
- references/.provenance/schemas.md.yaml 1.5 KB
- references/schemas.md 12 KB
- scripts/__init__.py 0 B runs code
- scripts/.provenance/__init__.py.yaml 1.5 KB
- scripts/.provenance/aggregate_benchmark.py.yaml 1.5 KB
- scripts/.provenance/generate_report.py.yaml 1.5 KB
- scripts/.provenance/improve_description.py.yaml 1.5 KB
- scripts/.provenance/package_skill.py.yaml 1.5 KB
- scripts/.provenance/quick_validate.py.yaml 1.5 KB
- scripts/.provenance/run_eval.py.yaml 1.5 KB
- scripts/.provenance/run_loop.py.yaml 1.5 KB
- scripts/.provenance/utils.py.yaml 1.5 KB
- scripts/aggregate_benchmark.py 14 KB runs code
- scripts/generate_report.py 12 KB runs code
- scripts/improve_description.py 11 KB runs code
- scripts/package_skill.py 4.1 KB runs code
- scripts/quick_validate.py 3.9 KB runs code
- scripts/run_eval.py 11 KB runs code
- scripts/run_loop.py 13 KB runs code
- scripts/utils.py 1.6 KB runs code
- SkillInstallation.md 1.7 KB
- SkillStructure.md 5.0 KB
- UserConfigSchema.md 2.7 KB
- ValidateWorkflow.md 1.6 KB
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.
- 3d ago First seen · 66 lines · 78 tokens per session scan A 92201e60243b
ForgeSkill is a skill published in the GitHub repository N4M3Z/forge-core (5 stars, last pushed 14d ago), licensed EUPL-1.2. It adds 78 tokens to every session and 1,235 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…