Borrowing it
Nothing to install: this file belongs to j5ik2o/event-store-adapter-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/j5ik2o/event-store-adapter-js/main/.agents/skills/skill-forge/SKILL.mdgit clone --depth 1 https://github.com/j5ik2o/event-store-adapter-jsWrote 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/j5ik2o/event-store-adapter-js/skill-forge)<a href="https://agentmods.dev/skills/j5ik2o/event-store-adapter-js/skill-forge"><img src="https://agentmods.dev/badge/skills/j5ik2o/event-store-adapter-js/skill-forge/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/j5ik2o/event-store-adapter-js/skill-forge"><img src="https://agentmods.dev/badge/skills/j5ik2o/event-store-adapter-js/skill-forge.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.00208 | $0.08379 |
| Opus 5 | $0.00104 | $0.04189 |
| Sonnet 5 | $0.00042 | $0.01676 |
| Haiku 4.5 | $0.00021 | $0.00838 |
Grade A, and why
skill-forge 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 7d 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.
This is a copy
86% identical to skill-creator — 180 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Forge
A skill for creating new skills and iteratively improving them.
At a high level, the process of creating a skill goes like this:
- Decide what you want the skill to do and roughly how it should do it
- Write a draft of the skill
- Create a few test prompts and run claude-with-access-to-the-skill on them
- Help the user evaluate the results both qualitatively and quantitatively
- While the runs happen in the background, draft some quantitative evals if there aren't any (if there are some, you can either use as is or modify if you feel something needs to change about them). Then explain them to the user (or if they already existed, explain the ones that already exist)
- Use the
eval-viewer/generate_review.pyscript to show the user the results for them to look at, and also let them look at the quantitative metrics
- Rewrite the skill based on feedback from the user's evaluation of the results (and also if there are any glaring flaws that become apparent from the quantitative benchmarks)
- Repeat until you're satisfied
- Expand the test set and try again at larger scale
Your job when using this skill is to figure out where the user is in this process and then jump in and help them progress through these stages. So for instance, maybe they're like "I want to make a skill for X". You can help narrow down what they mean, write a draft, write the test cases, figure out how they want to evaluate, run all the prompts, and repeat.
On the other hand, maybe they already have a draft of the skill. In this case you can go straight to the eval/iterate part of the loop.
Of course, you should always be flexible and if the user is like "I don't need to run a bunch of evaluations, just vibe with me", you can do that instead.
Then after the skill is done (but again, the order is flexible), you can also run the skill description improver, which we have a whole separate script for, to optimize the triggering of the skill.
Cool? Cool.
Communicating with the user
What ships with it
32 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.
- agents/analyzer.md 10 KB
- agents/comparator.md 7.1 KB
- agents/grader.md 8.8 KB
- assets/eval_review.html 6.9 KB
- eval-viewer/generate_review.py 16 KB runs code
- eval-viewer/viewer.html 44 KB
- evals/evals.json 2.3 KB
- justfile 231 B
- pyproject.toml 287 B
- references/schemas.md 12 KB
- scripts/__init__.py 0 B runs code
- scripts/aggregate_benchmark.py 14 KB runs code
- scripts/ci/verify_skill_md.sh 1.3 KB runs code
- scripts/ci/verify.sh 1.0 KB runs code
- scripts/generate_report.py 13 KB runs code
- scripts/improve_description.py 12 KB runs code
- scripts/package_skill.py 4.1 KB runs code
- scripts/quick_validate.py 3.9 KB runs code
- scripts/run_eval_claude.py 8.3 KB runs code
- scripts/run_eval_codex.py 4.0 KB runs code
- scripts/run_eval.py 7.1 KB runs code
- scripts/run_loop.py 14 KB runs code
- scripts/utils.py 5.0 KB runs code
- tests/__init__.py 0 B runs code
- tests/test_aggregate_benchmark.py 872 B runs code
- tests/test_improve_description.py 1.9 KB runs code
- tests/test_run_eval.py 32 KB runs code
- tests/test_run_loop.py 2.4 KB runs code
- tests/test_skill_docs.py 1.4 KB runs code
- tests/test_skill_md.py 4.5 KB runs code
- tests/test_utils.py 10 KB runs code
- uv.lock 20 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.
- 7d ago First seen · 567 lines · 208 tokens per session scan A 85add02361b0
skill-forge is a skill published in the GitHub repository j5ik2o/event-store-adapter-js (24 stars, last pushed today), licensed Apache-2.0. It adds 208 tokens to every session and 8,379 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to skill-creator, differing in 180 lines, and is treated as a copy.
Other skills, from other repositories
cratis-specifications-csharp
Write C# specifications with Cratis.Specifications using the Establish/Because/should pattern and the for/when/and folder hierarchy. Use when adding or restructuring C# specs in any Cratis repository, choosing between an isolated unit spec and an in-process scenario spec, or building reusable given/ contexts. Do not…
cratis-stage-rendering-and-sandbox
Understand what Cratis Stage actually does with a Screenplay .play model today — the deterministic artifact render plan and the narrow model shape it admits, the disposable cratis/stage sandbox container, and the cratis/stage-specrunner model-level specification job. Use when deciding whether Stage can render a model…
cratis-application-slice-specifications
Specify the backend behavior of an event-sourced Cratis application slice with the in-process scenario family — CommandScenario, EventScenario, ReadModelScenario and ReactorScenario — including what to cover for each slice type and where the specification files live. Use when adding or changing backend behavior in an…
cratis-chronicle-event-constraints
Enforce append-time uniqueness in Chronicle with the [Unique] attribute, [RemoveConstraint], and IConstraint, and specify the violation with EventScenario. Use when a rule must hold at the event store rather than in a command, so two concurrent appends cannot both win. Do not use for ordinary command input validation…
cratis-specification-by-example
Structure and name executable specifications the Cratis way — one behavior per specification, a for/when/and path that reads as an English sentence, layered given/ contexts, and an explicit decision about what is not worth specifying. Use when deciding how to organize, name, or scope specifications in any language. Do…
cratis-specs-csharp
Step-by-step guidance for writing C# specs in Cratis with BDD Specification by Example — the Establish/Because/should pattern, for/when/and folder hierarchy, reusable given/ contexts, NSubstitute mocking, and the in-process scenario family. Use when writing C# unit or integration specs or structuring the for/when/and…