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 commands/dotoricode/tink-harness/setupgit clone --depth 1 https://github.com/dotoricode/tink-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.00015 | $0.02047 |
| Opus 5 | $0.00008 | $0.01024 |
| Sonnet 5 | $0.00003 | $0.00409 |
| Haiku 4.5 | $0.00002 | $0.00205 |
Grade A, and why
setup 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 yesterday.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tink:setup
Set up Tink for Claude Code.
Goal
Prepare one small self-growing harness system that helps Claude choose/build harnesses, avoid repeated mistakes, and remember reusable lessons only after approval.
Setup config includes completion_policy:
normal: Tink reports done with the best evidence available for the run.strict: Tink must not call a run done until.tink/current/contract.json,.tink/current/verification.json, and.tink/current/evidence.mdexist, required checks are accounted for, and remaining risk is stated.
Do not turn this into a broad setup menu unless the user asks. Default to normal and explain strict as an optional "no evidence, no done" policy.
Interaction policy
Always call the AskUserQuestion tool for choice prompts. Do not render ❯ text format. Do not ask the user to type a number inline.
Map prompt content to AskUserQuestion fields:
question: the full question textheader: max 12-character tag (e.g. "언어 선택", "설치 범위", "Git 설정")label: 1–5 word option name. Add "(권장)" if recommended.description: explanatory text for the option
Use Korean field values when .tink/config.json language is ko or auto with Korean input; use English otherwise.
Setup review mode
If .tink/config.json already exists, do not jump straight to git tracking. First show a short current-settings review, then ask what to change.
Use this wording in Korean:
현재 Tink 설정입니다.
- 언어: {language}
- 범위 (Scope): {install_scope}
- 톤 (Tone): calm, clear, concise, no jokes
- Hook: {hook_scope}
- 완료 정책: {completion_policy}
- Git 추적: {git_policy_or_inferred_policy}
톤은 선택 항목이 아니라 Tink의 고정 정책입니다. 조용하고 명확하게, 농담 없이 답하는 것을 기본으로 합니다.
? 무엇을 바꿀까요?
❯ 1. 그대로 사용 (권장)
2. 언어 변경
3. 범위 변경
4. 훅/Git 변경
If the user chooses 그대로 사용, summarize available commands and stop. Do not re-ask git tracking.
If the user chooses 훅/Git 변경, first walk through the Git tracking question, then the Hook registration question.
Legacy Tiny migration
If .tiny/, .claude/commands/tiny/, .claude/commands/tiny-use.md, or output that recommends /tiny:use is present, treat it as legacy state from the old Tiny/Tink prototype. Do not keep recommending /tiny:use.
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.
- yesterday First seen · 193 lines · 15 tokens per session scan A 204be5960091
setup is a command published in the GitHub repository dotoricode/tink-harness (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 2,047 once invoked, about $0.0001 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 commands, from other repositories
diagnose
RTK environment diagnostics - Checks installation, hooks, version, command routing.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
worktree
Create a git worktree for isolated feature/fix work.