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/chachamaru127/codex-harness/setup-toolsnpx skills add Chachamaru127/codex-harness --skill setup-toolsgit clone --depth 1 https://github.com/Chachamaru127/codex-harnessWhat 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.00078 | $0.01333 |
| Opus 5 | $0.00039 | $0.00666 |
| Sonnet 5 | $0.00016 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
setup-tools 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Tools Skill
Consolidates all tool setup commands into one unified interface.
Usage
/setup-tools # Show available options
/setup-tools ci # Setup CI/CD (GitHub Actions)
/setup-tools dev-tools # Setup AST-Grep + LSP (recommended)
/setup-tools lsp # Setup LSP only
/setup-tools mcp # Setup MCP server
/setup-tools opencode # Setup OpenCode.ai compatibility
/setup-tools codex # Setup Codex CLI compatibility
/setup-tools webhook # Setup GitHub Actions webhook
/setup-tools ui # Setup Harness UI
/setup-tools remotion # Setup Remotion video generation
/setup-tools skills # Update skills settings
Subcommands Reference
| Subcommand | Reference | Description |
|---|---|---|
ci |
references/ci-setup.md | CI/CD (GitHub Actions) |
dev-tools |
references/dev-tools-setup.md | AST-Grep + LSP |
lsp |
references/lsp-setup.md | LSP only |
mcp |
references/mcp-setup.md | MCP server |
opencode |
references/opencode-setup.md | OpenCode.ai |
codex |
references/codex-setup.md | Codex CLI |
webhook |
references/webhook-setup.md | GitHub Actions webhook |
remotion |
references/remotion-setup.md | Remotion video |
Execution Flow
- Parse subcommand from $ARGUMENTS
- If no subcommand, show available options and ask user
- Load corresponding reference file
- Execute setup steps from reference
- Verify configuration
Subcommand Details
/setup-tools ci - CI/CD Setup
Sets up GitHub Actions for automated testing and deployment.
Features: Lint, TypeScript check, Unit tests, E2E tests, Build check
/setup-tools dev-tools - Development Tools (Recommended)
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 164 lines · 78 tokens per session scan A af53c0a8da76
setup-tools is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 78 tokens to every session and 1,333 once invoked, about $0.0004 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.