Borrowing it
Nothing to install: this file belongs to CIrcui-try/Circuit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CIrcui-try/Circuit/main/.agents/skills/takeoff/SKILL.mdgit clone --depth 1 https://github.com/CIrcui-try/CircuitWrote 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/circui-try/circuit/takeoff)<a href="https://agentmods.dev/skills/circui-try/circuit/takeoff"><img src="https://agentmods.dev/badge/skills/circui-try/circuit/takeoff/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/circui-try/circuit/takeoff"><img src="https://agentmods.dev/badge/skills/circui-try/circuit/takeoff.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.00028 | $0.01338 |
| Opus 5.5 | $0.00011 | $0.00535 |
| Sonnet 5.5 | $0.00006 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
takeoff 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 2mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
이륙 시퀀스의 4단계 (Takeoff). develop 위에 리베이스하고 리모트에 push 한 뒤 PR 을 생성한다. 이 단계만 원격에 영향을 준다. 성공하면 임시 상태 파일(.Codex/state/<ISSUE>.*) 을 모두 삭제한다.
$ARGUMENTS 형식: <ISSUE-ID> [--force]. 예: /takeoff CIR-15.
인자 파싱
--force분리. 첫 토큰을<ISSUE>로.<ISSUE>없으면 사용법 안내 후 중단.
상태 파일 경로
MAIN_REPO_ROOT = $(git rev-parse --path-format=absolute --git-common-dir | xargs dirname)STATE_FILE = $MAIN_REPO_ROOT/.Codex/state/<ISSUE>.jsonISSUE_FILE = $MAIN_REPO_ROOT/.Codex/state/<ISSUE>.issue.mdPLAN_FILE = $MAIN_REPO_ROOT/.Codex/state/<ISSUE>.plan.md
자동 체이닝
상태 파일을 읽어 다음 순서로 실행:
STATE_FILE이 없으면 다른.Codex/state/*.json을 후보나 캐시로 사용하지 않는다. 사용자가 입력한<ISSUE>를 정답으로 보고/boarding <ISSUE> [--force]를 먼저 실행한 뒤STATE_FILE을 다시 읽는다. 그래도 없으면 boarding 실패로 보고 중단한다.boarding.done_at == null이거나--force→/boarding <ISSUE> [--force]. 채워져 있으면 스킵 메시지 한 줄.door_closing.done_at == null이거나--force→/door-closing <ISSUE> [--force]. 채워져 있으면 스킵.taxiing.done_at == null이거나--force→/taxiing <ISSUE> [--force]. 채워져 있으면 스킵.- 본 단계 진행.
자동 체이닝은 본 단계까지만 — landing 은 자동으로 호출하지 않는다.
자기 단계 실행 절차
- 스킵 판정:
takeoff.done_at이 채워져 있고--force가 없으면 종료. (다만 takeoff 성공 후 상태 파일은 삭제되므로 보통 이 케이스는 발생하지 않음.) - 워크트리 진입:
worktree_path로 cd. 경로가 없으면 사용자에게 안내 후 중단. - 상태 점검:
git status가 깨끗한지 확인. 미커밋 변경이 있으면 사용자에게 알리고 중단. - 티켓 상태 동기화: Linear 이슈가
Done/Canceled가 아니면 상태를In Progress로 직접 변경한다. - GitHub 인증 확인:
gh-auth-check스킬로 GitHub CLI 로그인 상태와 active account 를 확인한다. - develop 리베이스:
git fetch origin develop && git rebase origin/develop. 충돌 시 자동 해결 시도하지 말고 사용자에게 위임 후 중단. - 푸시:
- 첫 push:
git push -u origin <branch>. - 리베이스로 히스토리가 바뀌었고 리모트에 이미 같은 브랜치가 있으면 사용자 승인 후
git push --force-with-lease origin <branch>. develop/main으로의 직접 푸시는 금지.
- 첫 push:
- PR 생성:
gh pr create --base develop --head <branch>.- 제목:
<ISSUE> <type>: <English summary>예)CIR-15 fix: prevent white screen when adding waitlist entries. - 제목과 본문은 반드시 영어로 작성한다. 한국어를 쓰지 않는다.
- 본문: HEREDOC 으로 다음 형식. 모든 placeholder 내용도 영어로 쓴다.
- 제목:
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.
- 2mo ago First seen · 81 lines · 28 tokens per session scan A 897814dbb230
takeoff is a skill published in the GitHub repository CIrcui-try/Circuit (5 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,338 once invoked, about $0.0001 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
generator-fix-integrator
Internal Auto-Harness generator skill for worktree-merge fix integration. Use only inside the parallel Generator integrator when it is addressing named defects from QA or retest.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
comet-archive
Comet Phase 5: Archive. Invoke with /comet-archive. Merge delta specs into main specs with OpenSpec semantics, archive change.
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.