tfx-hooks

tfx-hooks is a skill for Claude Code from tellang/triflux. It costs 148 tokens per session (1,956 once invoked), scanned A, original, MIT.

A manager for Claude Code hooks and their execution order. Claude Code hooks are automatic commands attached to events, and an orchestrator is a single entry point that runs them in a chosen priority order.

In plain words
What is it for?
Use it to view hook status, preview or apply orchestration, restore the original settings, or manage individual hooks and their priorities.
Why use it?
It helps inspect, combine, reorder, enable, disable, or restore hooks when several hooks need coordinated execution. It can make triflux hooks run before other registered hooks.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Part of the triflux plugin — 29 skills, 1 agent, 12 hooks shipped together

Good fit Use it to view hook status, preview or apply orchestration, restore the original settings, or manage individual hooks and their priorities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tellang/triflux/tfx-hooks
Install

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.

Any agent
npx skills add tellang/triflux --skill tfx-hooks
Clone the repo
git clone --depth 1 https://github.com/tellang/triflux

Made for: Claude Code.

Or install triflux, the plugin that ships this one along with the rest of its 29 skills, 1 agent, 12 hooks.

Wrote 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.

agentmods badge for tfx-hooks

README.md
[![agentmods](https://agentmods.dev/badge/skills/tellang/triflux/tfx-hooks/github.svg)](https://agentmods.dev/skills/tellang/triflux/tfx-hooks)
Your own site
<a href="https://agentmods.dev/skills/tellang/triflux/tfx-hooks"><img src="https://agentmods.dev/badge/skills/tellang/triflux/tfx-hooks/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.

agentmods 80×15 button for tfx-hooks

Your own site · 80×15
<a href="https://agentmods.dev/skills/tellang/triflux/tfx-hooks"><img src="https://agentmods.dev/badge/skills/tellang/triflux/tfx-hooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 148 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,956 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00148 $0.01956
Opus 5 $0.00074 $0.00978
Sonnet 5 $0.00030 $0.00391
Haiku 4.5 $0.00015 $0.00196

Measured 9d ago against content hash 6c3760c44c1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

tfx-hooks 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 9d 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.

packages/triflux/skills/tfx-hooks/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

tfx-hooks — 훅 우선순위 관리자

Claude Code 훅의 실행 순서를 관리합니다. triflux 훅이 항상 최우선 실행되도록 보장합니다.

핵심 개념

Claude Code는 같은 이벤트에 매칭된 훅을 병렬 실행합니다. 순서 보장이 불가능합니다. triflux의 hook-orchestrator는 이벤트당 하나의 진입점을 두고, 내부에서 우선순위대로 순차 실행합니다.

settings.json → hook-orchestrator.mjs (단일 진입점)
                    ↓ hook-registry.json 읽기
                    ↓ priority 순 정렬
                    1. triflux 훅 (priority=0)
                    2. OMC 훅 (priority=50)
                    3. 외부 훅 (priority=100)

워크플로우

Step 1: 현재 상태 확인

Bash("node hooks/hook-manager.mjs status")

결과 JSON에서 orchestrated 필드로 적용 여부를 판단한다.

Step 2: 메인 메뉴 (AskUserQuestion)

question: "훅 관리 — 어떤 작업을 수행하시겠습니까?"
header: "Hook Manager"
options:
  - label: "현재 상태 보기"
    description: "settings.json 훅 스캔 + 오케스트레이터 적용 상태"
  - label: "오케스트레이터 적용"
    description: "모든 훅을 통합 — triflux 최우선 실행 보장"
  - label: "변경점 미리보기 (diff)"
    description: "적용 시 어떻게 바뀌는지 확인"
  - label: "원래대로 복원"
    description: "오케스트레이터 제거, 원래 settings.json 훅으로 복원"
  - label: "개별 훅 관리"
    description: "특정 훅 활성/비활성, 우선순위 변경"

Step 3: 선택에 따른 분기

"현재 상태 보기"
Bash("node hooks/hook-manager.mjs scan")

결과 JSON을 파싱하여 테이블로 표시:

## 현재 훅 상태

| 이벤트 | 훅 수 | 소스 |
|--------|-------|------|
| SessionStart | 4 | triflux(3), session-vault(1) |
| PreToolUse | 3 | triflux(1), omc(2) |
| ...    | ...   | ... |

오케스트레이터: ❌ 미적용 / ✅ 적용됨 (N개 이벤트)
"오케스트레이터 적용"

먼저 diff를 보여준 후 확인:

Bash("node hooks/hook-manager.mjs diff")

결과를 표시한 뒤 AskUserQuestion:

question: "위 변경을 적용하시겠습니까?"
header: "확인"
options:
  - label: "적용"
    description: "settings.json 백업 후 오케스트레이터 적용"
  - label: "취소"
    description: "변경 없이 돌아가기"

"적용" 선택 시:

Bash("node hooks/hook-manager.mjs apply")

적용 결과 표시:

✅ 오케스트레이터 적용 완료
   N개 이벤트 → 1개 오케스트레이터로 통합
   실행 순서: triflux(0) → OMC(50) → external(100)
   복원: /tfx-hooks → 원래대로 복원
   또는: triflux hooks restore
"변경점 미리보기 (diff)"
Bash("node hooks/hook-manager.mjs diff")

Read the full file on GitHub · 215 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 215 lines · 148 tokens per session scan A 6c3760c44c1d

Subscribe to this mod's changes

tfx-hooks is a skill published in the GitHub repository tellang/triflux (7 stars, last pushed yesterday), licensed MIT. It adds 148 tokens to every session and 1,956 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

lucia-chat

Set two agent sessions talking through the Luciazero Agent Bus and watch it live in a terminal: pick the pair, open the windows, read the transcript. Use for "ให้ codex กับ claude คุยกัน" or "watch the bus".

ohm41321/luciazero · 55 tokens

ready

Make an unfamiliar repository agent-ready with a verify command, smoke tests, guardrails, and project notes. Use for repository setup, agentic engineering, verify commands, hooks, or allowlists; skip when verification and scope are already clear.

ohm41321/luciazero · 50 tokens

handoff

Write a state capsule so the next session — or a different agent/harness — can resume unfinished work without re-deriving context. Use when a session is ending with work incomplete, when the user says "handoff", "pack up", "ส่งต่อ", "continue tomorrow", when switching between Claude Code and Codex mid-task, or when…

ohm41321/luciazero · 86 tokens

done

Run the closeout ritual before handing back non-trivial work; full verification, revert-probe honesty, independent review, and scope reporting. Use before declaring completion, opening a PR, wrapping up a change, or "ปิดงาน".

ohm41321/luciazero · 50 tokens

retro

Record durable lessons, null results, and footguns after hard work or debugging. Use when the user asks for a retro, dead ends need preserving, a task disproves an approach, or "จดบทเรียน". Keep repo knowledge separate from machine-local memory.

ohm41321/luciazero · 55 tokens

show

Visualize code structure, changes, and verification evidence in the smallest useful view. Use for connections, flows, diffs, file maps, Mermaid diagrams, evidence maps, or focused HTML; show facts and label unknowns.

ohm41321/luciazero · 47 tokens