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 jmagly/aiwg --skill contribute-startgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/contribute-start)<a href="https://agentmods.dev/skills/jmagly/aiwg/contribute-start"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/contribute-start.svg" alt="Measured on agentmods" 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.00025 | $0.01040 |
| Opus 5 | $0.00013 | $0.00520 |
| Sonnet 5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
contribute-start 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribute Start
You initialize a contribution workflow for AIWG itself: create a feature branch, configure DCO (Developer Certificate of Origin), link to a tracking issue, and set up a working directory for the contribution.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "I want to add a feature to AIWG" → init contribution for new feature
- "set up my branch for this fix" → init contribution for bug fix
- "how do I contribute?" → explain contribution flow and offer to initialize
- "start a PR" → initialize contribution and set up branch
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Contribute start | "contribute start" | Run aiwg contribute-start |
| New contribution | "new contribution" | Run aiwg contribute-start |
| Init contribution | "init contribution" | Run aiwg contribute-start |
| Start contributing | "start contributing to aiwg" | Run aiwg contribute-start |
| With issue | "start contribution for issue #42" | Run aiwg contribute-start --issue 42 |
| With description | "start a contribution for adding voice support" | Run aiwg contribute-start --description "adding voice support" |
Behavior
When triggered:
-
Extract intent:
- Is there an issue number to link? (e.g., "for issue #42")
- Is there a description to use for the branch name?
- What type of contribution: feature, fix, docs, refactor?
-
Run the appropriate command:
# Default: interactive contribution initialization aiwg contribute-start # Link to a specific tracking issue aiwg contribute-start --issue 42 # With branch description (slugified automatically) aiwg contribute-start --description "add voice support to deploy command" # Specify contribution type aiwg contribute-start --type feat aiwg contribute-start --type fix aiwg contribute-start --type docs -
Report the result — confirm the branch name, DCO status, and working directory path.
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.
- 5d ago First seen · 127 lines · 25 tokens per session scan A b806eaf3b048
contribute-start is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 1,040 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
implement-issue
Drive a GitHub issue from branch to pull request — read the issue, create a feature branch, implement the change, run the project's build and tests, then commit, push, and open a PR. Language and build-tool agnostic. Use when asked to implement, fix, or resolve a GitHub issue by number.
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
fest-execution
Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
camp-projects
Manage a camp's projects. Use when committing inside projects/, deciding status/pull/push scope (root vs submodule vs all), or creating/removing project worktrees.
flo
MoFlo ticket spell - analyze and execute GitHub issues.
gh
You have access to gh (GitHub CLI) for repository and project management.