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 cmdr-chara/codex-toolkit --skill toolchain-preflightgit clone --depth 1 https://github.com/cmdr-chara/codex-toolkitWrote 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/cmdr-chara/codex-toolkit/toolchain-preflight)<a href="https://agentmods.dev/skills/cmdr-chara/codex-toolkit/toolchain-preflight"><img src="https://agentmods.dev/badge/skills/cmdr-chara/codex-toolkit/toolchain-preflight/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/cmdr-chara/codex-toolkit/toolchain-preflight"><img src="https://agentmods.dev/badge/skills/cmdr-chara/codex-toolkit/toolchain-preflight.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00039 | $0.00512 |
| Opus 5.5 | $0.00016 | $0.00205 |
| Sonnet 5.5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
toolchain-preflight 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 24d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Toolchain Preflight
Resolve one supported local execution path, then get out of the way.
Trigger boundary
Use this skill when required executables or invocation behavior are unknown, or a task is blocked by shell/runtime/package-manager shims, incompatible local runtimes, quoting, browser binaries/capability, or text encoding.
Do not trigger when the repository's documented command already reaches the real task, for application debugging, deliberate dependency/runtime migrations, or final release judgment.
Required inputs
Resolve repository instructions, working-tree/user state, OS/shell, documented command, required runtime/executable/capability, first exact failure, and any policy constraints on installs/downloads.
Safety baseline
- Preserve uncommitted user work.
- Prefer existing documented/system/runtime paths before installs or environment mutation.
- Do not repeatedly retry an unchanged failing mechanism.
- Use scratch locations for probes that should not affect the repository.
- Do not bypass execution policy/security controls merely to make a command run.
Workflow
- Establish the documented path. Read repository instructions and exact command first.
- Resolve real executables. Distinguish shell shims/wrappers from underlying runtimes and package managers.
- Classify the failure. Missing executable, blocked shim, wrong version/architecture, stale virtual environment, quoting, browser capability, encoding, or actual application failure.
- Select one safe invocation. Prefer the least-mutating supported path.
- Probe once, then run the real task. A successful version probe is not enough; confirm the invocation reaches the repository task.
- Hand off immediately. Once the execution path works, application behavior belongs to its specialist.
Handoffs and interaction boundaries
Application failures go to debugging-investigator; planned version transitions to evolution; browser/app implementation to the owning builder; final integrated evidence to verification-and-release.
What ships with it
1 file 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.
- 24d ago Changed · -123 lines · -67 tokens per session 4f5c6331eb9b
- 1mo ago First seen · 171 lines · 106 tokens per session scan A 194832e27224
toolchain-preflight is a skill published in the GitHub repository cmdr-chara/codex-toolkit (2 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 512 once invoked, about $0.0002 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-31.
Other skills, from other repositories
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
code-coherence-review
Reviews code and plans for logic coherence, correctness, and structural integrity.