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/dsifry/metaswarm/create-issuenpx skills add dsifry/metaswarm --skill create-issuegit clone --depth 1 https://github.com/dsifry/metaswarmWhat 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.00025 | $0.02799 |
| Opus 5 | $0.00013 | $0.01399 |
| Sonnet 5 | $0.00005 | $0.00560 |
| Haiku 4.5 | $0.00003 | $0.00280 |
Grade A, and why
create-issue 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 3d 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue Skill
Create comprehensive, well-structured GitHub issues with embedded agent instructions for autonomous PR lifecycle management.
Overview
This skill generates GitHub issues that are self-contained work packets. Each issue includes:
- Problem/Feature specification with clear scope
- Technical specification with types, schemas, and API design
- TDD Implementation Plan with test-first cycles
- Acceptance Criteria checklist
- Agent Instructions for complete PR lifecycle (implementation → review → merge)
Usage
/create-issue
Interactive Flow
Step 1: Issue Type
Ask the user:
What type of issue is this?
1. Feature - New functionality
2. Bug - Something broken
3. Refactor - Improving existing code
Step 2: Brief Description
Brief description of the problem or feature? (1-2 sentences)
Step 3: Complexity Assessment
What's the estimated complexity?
1. Simple (< 1 day)
2. Medium (2-5 days)
3. Complex (> 1 week)
Step 4: Context Gathering
Any related files, services, or issues I should reference?
(Or say "explore codebase" and I'll investigate)
Step 5: Generate Issue
Based on inputs, generate the full issue using the appropriate template below.
Issue Templates
Feature Template
## Summary
[1-2 sentence description]
**Complexity**: [simple|medium|complex]
**Estimated Effort**: [X days]
---
## Problem
[What problem does this solve? Why is it needed?]
### Evidence
[Logs, metrics, user reports, or reasoning]
### Scope
- IN SCOPE: [what's included]
- OUT OF SCOPE: [what's explicitly NOT included]
---
## Architecture Decision
**Decision**: [What approach will be taken]
**Rationale**: [Why this approach, why NOT alternatives]
---
## Technical Specification
### Types/Interfaces
```typescript
// Key type definitions
```
Zod Schemas (if applicable)
// Validation schemas
API Endpoints (if applicable)
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.
- 3d ago First seen · 497 lines · 25 tokens per session scan A ef754d96d526
create-issue is a skill published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 2,799 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-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…