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/seanhogg/builderforce.ai/builderforcenpx skills add SeanHogg/Builderforce.ai --skill builderforcegit clone --depth 1 https://github.com/SeanHogg/Builderforce.aiWhat 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.00061 | $0.02510 |
| Opus 5 | $0.00030 | $0.01255 |
| Sonnet 5 | $0.00012 | $0.00502 |
| Haiku 4.5 | $0.00006 | $0.00251 |
Grade A, and why
builderforce 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
builderForceAgents: Multi-Agent Developer System
builderForceAgents is a developer-first multi-agent system for comprehensive software development workflows.
Quick Start
Initialize a Project
# Initialize builderforce in current project
builderforce init
# Check project status
builderforce project status
Use builderForceAgents Tools
Once initialized, use builderforce tools in agent conversations:
# Analyze code structure
code_analysis projectRoot:/path/to/project
# Query project knowledge
project_knowledge projectRoot:/path/to/project query:all
# Analyze git history
git_history projectRoot:/path/to/project limit:50
# Orchestrate a feature workflow
orchestrate workflow:feature description:"Add user authentication"
# Check workflow status
workflow_status workflowId:abc-123
# Memory-aware operations
index-memory
suggest-memory
share-memory
delegate-to <agentNodeId>
Core Capabilities
1. Deep Code Understanding
- AST Parsing: Extracts functions, classes, interfaces, types
- Dependency Graphs: Tracks file dependencies and impact
- Code Maps: Semantic understanding of codebase structure
- Git History: Evolution, blame, and change patterns
2. Memory-Aware Orchestration
BuilderForceAgents now integrates with the structured memory index:
- index-memory: Build or rebuild
.builderforce/memory-index.jsonfrom daily logs - suggest-memory: Run advisory scan for stale entries, duplicates, and semantic clusters
- share-memory: Opt-in push of index to peer agentNodes (requires
.builderforce/memory-sync/config.yaml) - delegate-to : Route specific subtasks to specialized agentNodes in the fleet
The memory index enables:
- Fast lookup of past decisions and lessons
- Cross-agentNode coordination (when sharing enabled)
- Automated suggestion scans (non-destructive)
- Pre-task context enrichment (fetches relevant past entries)
3. Multi-Agent Orchestration
Coordinate specialized agents for complex tasks:
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 · 451 lines · 61 tokens per session scan A 659581059d41
builderforce is a skill published in the GitHub repository SeanHogg/Builderforce.ai (5 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 2,510 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-31.
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…