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 1A7432/loreweaver --skill skill-forgegit clone --depth 1 https://github.com/1A7432/loreweaverWrote 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/1a7432/loreweaver/skill-forge)<a href="https://agentmods.dev/skills/1a7432/loreweaver/skill-forge"><img src="https://agentmods.dev/badge/skills/1a7432/loreweaver/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/1a7432/loreweaver/skill-forge"><img src="https://agentmods.dev/badge/skills/1a7432/loreweaver/skill-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00457 |
| Opus 5.5 | $0.00021 | $0.00183 |
| Sonnet 5.5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
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 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.
What it actually says
Skill forge
You can author entirely new KP skills, not just use the ones already installed.
When the keeper describes a play style they want this table to have -- a
tone, a recurring mechanic, a narrative focus that no existing skill already
covers -- call generate_skill with a clear, self-contained description of
it. Only call it when the keeper is explicitly asking for a new skill to be
authored; never speculatively, and never in response to ordinary play.
A good description to pass along:
- names the play style plainly (e.g. "investigation clue-tracking", "grim survival horror", "a courtly-intrigue faction game")
- says what it should emphasize, in tone or mechanics
- says what, if anything, it should let the Keeper do differently
What makes a good skill: a focused scope (one play style, not a grab-bag of everything), prompt-only guidance unless the play style truly cannot work without unlocking a tool that already exists elsewhere in the toolset, a voice that stays tasteful and consistent with the rest of the table, and a crisp one-paragraph description that tells a keeper when to enable it. Never ask for a skill to invent brand-new tool names -- a skill can only unlock tools that already exist.
After generate_skill responds, tell the keeper plainly what was created (or
why it wasn't, if it failed) and remind them a new skill still needs to be
turned on for this room with .skill enable <id> before it takes effect.
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 · 42 lines · 52 tokens per session scan A 378b418cd461
Skill forge is a skill published in the GitHub repository 1A7432/loreweaver (67 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 457 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-30.
Other skills, from other repositories
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
motion
Reconstruct a skeleton from calibrated mesh projections and sequential VLM joint annotations, then fit joints and skin weights. Generate motion from joint-position trajectories, rhythm and contact constraints through IK; refine bone orientation against the action, then export, retarget and validate on the target mesh.
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
threejs-exposure-color-grading
Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.