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/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/jmagly/aiwg/contribute-start"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/contribute-start.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.00025 | $0.01040 |
| Opus 5.5 | $0.00010 | $0.00416 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 127 lines · 25 tokens per session scan A b806eaf3b048
contribute-start is a skill published in the GitHub repository jmagly/aiwg (225 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,040 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
launch
Planning releases and reporting delivery work from GitHub PR history. Use when versioning, CHANGELOGs, rollout or rollback plans, engineering metrics, retrospectives, or stakeholder reports are needed.
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
monorepo-architect
Expert guide for designing and managing scalable monorepos using Turborepo, pnpm workspaces, and shared packages / Panduan ahli untuk merancang dan mengelola monorepo skalabel menggunakan Turborepo dan pnpm workspaces.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
pdm
Navigating delivery status read-only: reconciles planned scope (specs/roadmap/PRD) against implemented code for what's built vs left. Not for priority scoring (Rank) or AC conformance (Attest).