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/coding-agentnpx skills add SeanHogg/Builderforce.ai --skill coding-agentgit 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.00108 | $0.02907 |
| Opus 5 | $0.00054 | $0.01453 |
| Sonnet 5 | $0.00022 | $0.00581 |
| Haiku 4.5 | $0.00011 | $0.00291 |
Grade B, and why
coding-agent scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Model:** `gpt-5.2-codex` is the default (set in ~/.codex/config.toml) This is a copy
81% identical to coding-agent — 62 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Agent (bash-first)
Use bash (with optional background mode) for all coding agent work. Simple and effective.
Dependencies
This skill depends on the github skill (declared via requires.skills: ["github"]). The runtime auto-includes github whenever coding-agent is active, and will mark coding-agent unavailable if github's own requirement (gh CLI) is not satisfied. Use the github skill for PR/issue/CI operations — this skill drives the code edits.
Repo Preparation (managed — do not hand-roll)
Note: When a coding agent runs against a repo-bound ticket or dispatch, the runtime prepares the workspace for you through a single modular repo-sync strategy (
src/infra/repo-sync.ts) — you do not clone or "check if it's the latest code" by hand:
- Per-dispatch runs get a fresh shallow clone of the latest default branch on a new working branch.
- Per-ticket runs reuse one shared workspace: it is cloned once, then refreshed to the latest default branch on reuse only when the tree is clean (uncommitted WIP from a prior agent is preserved, never clobbered), and the ticket branch is checked out idempotently.
Only fall back to manual
git clone/mktemp -d && git initfor scratch/one-shot work that is NOT tied to a ticket or dispatch (see Quick Start below).
⚠️ PTY Mode Required!
Coding agents (Codex, Claude Code, Pi) are interactive terminal applications that need a pseudo-terminal (PTY) to work correctly. Without PTY, you'll get broken output, missing colors, or the agent may hang.
Always use pty:true when running coding agents:
# ✅ Correct - with PTY
bash pty:true command:"codex exec 'Your prompt'"
# ❌ Wrong - no PTY, agent may break
bash command:"codex exec 'Your prompt'"
Bash Tool Parameters
| Parameter | Type | Description |
|---|---|---|
command |
string | The shell command to run |
pty |
boolean | Use for coding agents! Allocates a pseudo-terminal for interactive CLIs |
workdir |
string | Working directory (agent sees only this folder's context) |
background |
boolean | Run in background, returns sessionId for monitoring |
timeout |
number | Timeout in seconds (kills process on expiry) |
elevated |
boolean | Run on host instead of sandbox (if allowed) |
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 · 305 lines · 108 tokens per session scan B 6f43af2b375e
coding-agent is a skill published in the GitHub repository SeanHogg/Builderforce.ai (5 stars, last pushed 2d ago), licensed MIT. It adds 108 tokens to every session and 2,907 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 81% identical to coding-agent, differing in 62 lines, and is treated as a copy.
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…