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 J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill spawn-taskgit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/spawn-task)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/spawn-task"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/spawn-task/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/j-star-films-studios/vibecode-protocol-suite/spawn-task"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/spawn-task.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.00017 | $0.00660 |
| Opus 5.5 | $0.00007 | $0.00264 |
| Sonnet 5.5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
spawn-task 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawn Task Skill
Create detailed task prompts that another agent (or future self) can execute without additional context.
When to Use
- Breaking down complex features
- Creating implementation specs
- When user says "spawn a task for..."
- Planning multi-phase work
Task Discovery
Gather from user:
- Task Description: What needs to be done?
- Priority: High / Medium / Low
- Scope: What's included/excluded?
- Timeline: Expected completion (optional)
Current State Analysis
# Check related files
find src -name "*relevant*" -type f
# Check documentation
ls docs/features/
# Check GitHub issues
gh issue list --search "[related term]"
Task Prompt Template
Create docs/tasks/[TaskName].md:
# 🎯 Task: [Task Name]
**Objective:** [Clear, measurable goal]
**Priority:** [High/Medium/Low]
**Scope:** [What's included/excluded]
---
## 📋 Requirements
### Functional Requirements
- **[REQ-001]** [Requirement with acceptance criteria]
### Technical Requirements
- **[TECH-001]** [Technical specification]
---
## 🏗️ Implementation Plan
### Phase 1: Setup
- [ ] [Setup task]
### Phase 2: Core Implementation
- [ ] [Core task]
### Phase 3: Enhancement
- [ ] [Enhancement task]
### Phase 4: Testing & Documentation
- [ ] [Testing task]
---
## 📁 Files to Create/Modify
| File | Action | Purpose |
|------|--------|---------|
| `src/features/[Feature]/...` | Create | [Purpose] |
---
## ✅ Success Criteria
### Code Quality
- [ ] TypeScript compliant (no `any`)
- [ ] Passes ESLint
- [ ] Unit tests with >80% coverage
### Performance
- [ ] Bundle size increase < 5KB
- [ ] Load time < 1.5s
### Functionality
- [ ] All requirements implemented
- [ ] Mobile responsive
---
## 🔗 Dependencies
**Depends on:** [Other components]
**Used by:** [Components that use this]
---
## 🚀 Getting Started
1. Read this task prompt completely
2. Review related files
3. Begin with Phase 1
4. Provide progress updates after each phase
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 · 131 lines · 17 tokens per session scan A 732ca5920ae1
spawn-task is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 7d ago), licensed ISC. It adds 17 tokens to every session and 660 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-08-30.
Other skills, from other repositories
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.
aiwg-regenerate-copilot
Regenerate copilot-instructions.md for GitHub Copilot with vendor-specific content only.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.
checkpoint
Create, list, or recover mid-workflow checkpoints so interrupted work resumes from a known-good position.