list

list is a command for Claude Code from dotoricode/tink-harness. It costs 11 tokens per session (1,412 once invoked), scanned A, original, MIT.

A command for inspecting Tink, a system that organizes reusable work procedures called harnesses, and their recent usage.

In plain words
What is it for?
Use it to review Tink harnesses, separate task-running procedures from management procedures, and identify custom or possibly outdated entries.
Why use it?
It shows which procedures are available and which were recently used without opening every procedure or raw log.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the tink plugin — 9 skills, 9 commands, 1 hook shipped together

Good fit Use it to review Tink harnesses, separate task-running procedures from management procedures, and identify custom or possibly outdated entries.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/dotoricode/tink-harness/list
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.

Clone the repo
git clone --depth 1 https://github.com/dotoricode/tink-harness

Made for: Claude Code.

Or install tink, the plugin that ships this one along with the rest of its 9 skills, 9 commands, 1 hook.

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 list

README.md
[![agentmods](https://agentmods.dev/badge/commands/dotoricode/tink-harness/list/github.svg)](https://agentmods.dev/commands/dotoricode/tink-harness/list)
Your own site
<a href="https://agentmods.dev/commands/dotoricode/tink-harness/list"><img src="https://agentmods.dev/badge/commands/dotoricode/tink-harness/list/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 list

Your own site · 80×15
<a href="https://agentmods.dev/commands/dotoricode/tink-harness/list"><img src="https://agentmods.dev/badge/commands/dotoricode/tink-harness/list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,412 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.
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.00011 $0.01412
Opus 5.5 $0.00004 $0.00565
Sonnet 5.5 $0.00002 $0.00282
Haiku 4.5 $0.00001 $0.00141

Measured 2mo ago against content hash f77236a3cf4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

.claude/commands/tink/list.md · 106 lines

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

  1. Read .tink/harnesses/index.json.
  2. Read only compact usage metadata from .tink/runs/ (frontmatter selected_harnesses / actually_loaded_harnesses + dates), .tink/maintenance/ledger.jsonl, and .tink/maintenance/weave-queue.json. Do not load raw logs.
  3. Treat .tink/current/ as weak evidence unless it is clearly from the same active conversation. If context is uncertain, label it stale current candidate, not proof of usage.
  4. 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: synthesized in index.json (created in this repo, not part of the default set). If a synthesized harness also matches a meta name, prefer meta.
  5. Compute the signal per harness:
    • 🟢 active — appears in any .tink/runs/*.md frontmatter or .tink/maintenance/ledger.jsonl entry.
    • ⚪ unknown — no run/ledger/memory evidence. Do not call it quiet or candidate for purge from the static index alone. Do not infer non-use from missing evidence.
  6. Show all three categories every time, even when one is empty. For an empty category, render _(아직 없음)_ (or the English equivalent if the project language is en) instead of an item list.
  7. Do not output the evidence field. Usage is now compressed into signal.

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.

Read the full file on GitHub · 106 lines

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. 2mo ago First seen · 106 lines · 11 tokens per session scan A f77236a3cf4f

Subscribe to this mod's changes

list is a command published in the GitHub repository dotoricode/tink-harness (1 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 1,412 once invoked, about $0.0000 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.

Related

list compared with commands from other repositories

list next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
listdotoricode/tink-harnessCommand13mo agoMITA11Claude Code
audit-agents-skillsFlorianBruniaux/claude-code-ultimate-guideCommand6.4ktodayCC-BY-SA-4.0A20Claude Code
security-auditFlorianBruniaux/claude-code-ultimate-guideCommand6.4ktodayCC-BY-SA-4.0A0Claude Code
worktreeFlorianBruniaux/claude-code-ultimate-guideCommand6.4ktodayCC-BY-SA-4.0A11Claude Code
diff-docsFlorianBruniaux/claude-code-ultimate-guideCommand6.4ktodayCC-BY-SA-4.0A15Claude Code
init-docsFlorianBruniaux/claude-code-ultimate-guideCommand6.4ktodayCC-BY-SA-4.0A13Claude Code
app-architectVKirill/claude-lane-stackCommand1248d agoMITA14Claude Code