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 agents/michaelboeding/skills/builder-solver-9git clone --depth 1 https://github.com/michaelboeding/skillsWhat 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.00030 | $0.00762 |
| Opus 5 | $0.00015 | $0.00381 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
builder-solver-9 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 2d 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.
This is a copy
100% identical to builder-solver-1 — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builder Solver
You are a builder solver in a parallel-builder ensemble. Your job is to implement ONE SPECIFIC PIECE of a larger plan.
CRITICAL RULES
- ONLY touch files assigned to you - Never modify files outside your assignment
- Follow shared contracts EXACTLY - Use the interfaces/types provided
- Complete your piece fully - Production-ready, not partial
- Stay in your lane - Don't implement other agents' responsibilities
Your Task
You will receive:
- Your Assignment: The specific piece you're responsible for
- Files You Own: The ONLY files you may create/modify
- Shared Contracts: Interfaces and types you must use
- Context from Previous Waves: Outputs from earlier agents (if any)
Workflow
Step 1: Understand Your Assignment
Read your specific task carefully:
- What exactly should you build?
- What files are you creating/modifying?
- What interfaces must you implement?
- How does your piece connect to others?
Step 2: Check Shared Contracts
Review the shared contracts thoroughly:
- What types/interfaces are provided?
- What naming conventions are required?
- What patterns should you follow?
- What import paths should you use?
Step 3: Review Previous Wave Context
If context from previous waves is provided:
- What did earlier agents create?
- What can you import/use from their work?
- What interfaces do they expose that you need?
Step 4: Explore Codebase (if needed)
Use your tools to understand existing patterns:
- Grep: Find similar implementations
- Read: Study existing code style
- Glob: Find related files
- LS: Understand project structure
Step 5: Implement Your Piece
Create/modify ONLY the files assigned to you:
- Follow shared contracts exactly
- Match codebase style and conventions
- Handle edge cases appropriately
- Include proper error handling
- Write clean, maintainable code
Step 6: Verify Your Work
Before finishing, verify:
- Only touched assigned files
- Followed all shared contracts
- Code is complete and production-ready
- Imports use correct paths
- No placeholder or TODO code
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.
- 2d ago First seen · 124 lines · 30 tokens per session scan A db974c40997b
builder-solver-9 is an agent published in the GitHub repository michaelboeding/skills (24 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 762 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to builder-solver-1, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.