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 agentmods add skills/warpdotdev/oz-for-oss/bootstrap-issue-confignpx skills add warpdotdev/oz-for-oss --skill bootstrap-issue-configgit clone --depth 1 https://github.com/warpdotdev/oz-for-ossWrote 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/warpdotdev/oz-for-oss/bootstrap-issue-config)<a href="https://agentmods.dev/skills/warpdotdev/oz-for-oss/bootstrap-issue-config"><img src="https://agentmods.dev/badge/skills/warpdotdev/oz-for-oss/bootstrap-issue-config.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 | $0.00063 | $0.01270 |
| Opus 5 | $0.00032 | $0.00635 |
| Sonnet 5 | $0.00013 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
bootstrap-issue-config 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bootstrap-issue-config — 89% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap issue triage configuration
Analyze the target repository and generate (or update) the issue triage configuration files used by the triage-new-issues workflow.
Outputs
This skill produces two files:
.github/issue-triage/config.json— label definitions used during triage..github/STAKEHOLDERS— CODEOWNERS-style ownership mappings from path patterns to GitHub usernames.
Workflow
1. Discover existing labels
- Use
gh label list --repo <owner>/<repo> --limit 200 --json name,color,descriptionto fetch all labels currently defined on the repository. - Classify each label into one of three categories:
- area labels — identify a component or subsystem (e.g.
area:api,area:docs). - feature labels — identify a capability or request type (e.g.
enhancement,bug,documentation). - status labels — identify workflow state (e.g.
triaged,needs-info,wontfix).
- area labels — identify a component or subsystem (e.g.
- If the repository has very few or no labels, seed the config with sensible defaults:
triaged(status),bug(feature),enhancement(feature),documentation(feature),needs-info(status),duplicate(status)repro:high,repro:medium,repro:low,repro:unknown(status)
2. Analyze recent issues
- Use
gh issue list --repo <owner>/<repo> --state all --limit 100 --json number,title,labels,createdAtto fetch recent issues. - If issues use labels that are not yet captured, add them to the appropriate category.
- Look at
.github/ISSUE_TEMPLATE/for template files — template names and labels referenced in templates can inform label discovery.
3. Generate or update config.json
- Read any existing
.github/issue-triage/config.json. - Merge newly discovered labels into the existing
labelsobject. Do not remove labels that already exist in the config — only add or update. - The config must contain only the
labelskey. Do not includestakeholdersordefault_experts. - Each label entry should have
color(6-character hex without#) anddescription(one-sentence summary). - Write the result to
.github/issue-triage/config.json. - Validate with
jq . .github/issue-triage/config.json.
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.
- 4d ago First seen · 102 lines · 63 tokens per session scan A 472b2878488a
bootstrap-issue-config is a skill published in the GitHub repository warpdotdev/oz-for-oss (304 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 1,270 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…