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/listgit 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.00011 | $0.01412 |
| Opus 5 | $0.00005 | $0.00706 |
| Sonnet 5 | $0.00002 | $0.00282 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
list 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tink:list
List available Tink harnesses without loading every harness body.
Procedure
- Read
.tink/harnesses/index.json. - Read only compact usage metadata from
.tink/runs/(frontmatterselected_harnesses/actually_loaded_harnesses+ dates),.tink/maintenance/ledger.jsonl, and.tink/maintenance/weave-queue.json. Do not load raw logs. - Treat
.tink/current/as weak evidence unless it is clearly from the same active conversation. If context is uncertain, label itstale current candidate, not proof of usage. - Classify every harness into exactly one of three categories:
- working — directly performs or gates tasks (e.g.
ship,requirements-interview,plan-consensus,goal-checkpoint,delegation-brief). Generic work (code change, research, review, docs) runs on the base run without a harness, so it does not appear here. - meta — manages other harnesses or Tink itself. Treat these names as meta regardless of
kind:harness-synthesis,harness-curation,tink-feedback-apply. - custom (this repo) —
kind: synthesizedinindex.json(created in this repo, not part of the default set). If a synthesized harness also matches a meta name, prefer meta.
- working — directly performs or gates tasks (e.g.
- Compute the signal per harness:
- 🟢 active — appears in any
.tink/runs/*.mdfrontmatter or.tink/maintenance/ledger.jsonlentry. - ⚪ unknown — no run/ledger/memory evidence. Do not call it
quietorcandidate for purgefrom the static index alone. Do not infer non-use from missing evidence.
- 🟢 active — appears in any
- Show all three categories every time, even when one is empty. For an empty category, render
_(아직 없음)_(or the English equivalent if the project language isen) instead of an item list. - Do not output the
evidencefield. Usage is now compressed intosignal.
Output format
Always start with a header block that defines the fields and categories. Render each harness as a multi-line block — one field per line, never collapsed onto one line. Close with an assessment and command suggestions.
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 · 106 lines · 11 tokens per session scan A f77236a3cf4f
list is a command published in the GitHub repository dotoricode/tink-harness (1 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,412 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.
sync
Check guide/landing synchronization status.