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 contributor-onboardinggit 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/contributor-onboarding)<a href="https://agentmods.dev/skills/razaib-khan/forgeweave/contributor-onboarding"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/contributor-onboarding.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.00033 | $0.01772 |
| Opus 5 | $0.00016 | $0.00886 |
| Sonnet 5 | $0.00007 | $0.00354 |
| Haiku 4.5 | $0.00003 | $0.00177 |
Grade A, and why
Contributor Onboarding 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 8d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributor Onboarding
Purpose
This skill exists to turn a newcomer into a productive contributor within a single session. It provides a guided walkthrough of the ForgeWeave repository — the specs, the CLI, the template structure, and the contribution process — so the contributor understands the project's architecture and can pick an issue, set up their environment, and make their first PR with confidence.
ForgeWeave is a behavioral execution framework for AI agents inside development environments. It is not a general-purpose tool. This skill ensures every contributor understands that core identity before they write code.
When to Use
- A new contributor asks "where do I start?" or "how do I contribute?"
- A contributor has cloned the repo but hasn't set up their environment.
- A contributor needs help picking their first issue.
- During a PR review, a contributor's changes indicate they don't understand the project's deterministic-first philosophy.
When Not to Use
- The contributor has already made multiple PRs and understands the workflow — they need task-specific help, not onboarding.
- The question is about a specific technical issue (Python dependency conflict, an adapter bug) — route to the relevant skill or discussion.
- The contributor is asking about something outside ForgeWeave (general Python questions, third-party TUI issues) — route to external resources.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
contributor_level |
enum: beginner, intermediate, advanced |
Yes | How familiar the contributor is with Python CLI tools and agent frameworks |
interest_area |
enum: core, adapters, skills, agents, docs, templates, ci |
Yes | Which part of the project the contributor wants to work on |
has_setup_env |
boolean | No (default: false) | Whether the contributor has already run the development setup |
Expected Outputs
| Output | Description |
|---|---|
| Project map | A list of the key files and directories the contributor needs to understand for their interest area |
| Environment check | Report of what's set up and what's missing |
| Issue suggestions | 1-3 open issues matching their interest area, with links and difficulty labels |
| Next-step instructions | The exact commands and files they should look at next |
What ships with it
1 file 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.
- 8d ago First seen · 170 lines · 33 tokens per session scan A 71b91b5e1ab6
Contributor Onboarding is a skill published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,772 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
prd
A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.
product-discovery
Product discovery workflow with OST, assumption testing, and interview scripts.
client-onboarding
Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is customer-support), NOT renewals/churn past the…
planning
A guide for planning software features and turning requests into clear requirements. It uses EARS, a plain format for stating what a system must do under specific conditions.
auto-status
A project dashboard skill that reports the current specification status for a project and its submodules. A specification is a written description of what should be built and how it should behave.
squads-cli
Squads CLI — operate your AI workforce through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.