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 Razaib-khan/ForgeWeave --skill skill-authoringgit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/razaib-khan/forgeweave/skill-authoring)<a href="https://agentmods.dev/skills/razaib-khan/forgeweave/skill-authoring"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/skill-authoring.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.1 | $0.00030 | $0.02259 |
| Opus 5 | $0.00015 | $0.01130 |
| Sonnet 5 | $0.00006 | $0.00452 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
Skill Authoring 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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring
Purpose
A ForgeWeave skill is a versioned workflow bundle, not a single prompt file. This skill guides an agent through the process of identifying, designing, writing, and validating a new skill for the ForgeWeave framework. It exists to ensure every skill in the project meets the same quality bar: repeatable workflows become skills, deterministic steps become scripts, and uncertain outcomes are covered by eval checks.
When an agent is asked to "create a skill" or "write a SKILL.md", this skill provides the canonical process — from scoping the job, through structuring the bundle, to proving the skill works with an eval.
When to Use
- The agent is asked to create a new ForgeWeave skill.
- An existing skill needs revision, expansion, or restructuring.
- A contributor asks for guidance on the skill format.
- A review finds that a skill is missing sections, scripts, or evals.
- The agent needs to convert an ad-hoc workflow into a repeatable skill.
When Not to Use
- The work is a one-time task that will never be repeated — a skill is for repeatable jobs.
- The work is pure code that does not involve agent judgment — use a regular script or module instead.
- The work requires modifying the skill specification itself (
SKILL_SPEC.md); that should be handled as a specification change, not a skill invocation. - The agent is being asked to execute a skill, not create one — use the skill's own triggers instead.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
domain |
string | Yes | The repeatable job the skill should cover (e.g., "adapter implementation", "release verification") |
use_cases |
array of string | Yes | 2-3 concrete situations where this skill applies |
existing_steps |
string | No | Any existing workflow notes, prompts, or scripts the skill should be based on |
tui_targets |
array of enum | No (default: all four) | Which TUIs the skill should target: opencode, claude, gemini, qwen |
What ships with it
4 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.
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 · 221 lines · 30 tokens per session scan A d34016a0a7fc
Skill Authoring is a skill published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 2,259 once invoked, about $0.0002 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
author-skill
Use when authoring a NEW rsc skill or editing an existing one — scoping it to one job, writing the description that decides whether it ever loads, splitting the body into references/, writing its evals, auditing it against the rubric. NOT building a product feature (that is specify) and NOT designing an agent loop…
skill-authoring
Creates and structures SKILL.md files for AI coding agents, including YAML frontmatter, trigger phrases, directive instructions, decision trees, code examples, and verification checklists. Use when the user asks to write a new skill, create a skill file, author agent capabilities, generate skill documentation, or…
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
vs-crawler
Crawl websites (news, blogs, papers, GitHub, product docs, RSS feeds) into a fixed-schema JSONL file, then create a dataset and a searchable application in Viking AI Search. Supports one-time crawl and scheduled recurring crawl with automatic incremental sync.
pentest-playbook
7-phase pentest pipeline from passive recon to exploitation.