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 skills add dotoricode/tink-harness --skill tink-listgit clone --depth 1 https://github.com/dotoricode/tink-harnessWrote 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/dotoricode/tink-harness/tink-list)<a href="https://agentmods.dev/skills/dotoricode/tink-harness/tink-list"><img src="https://agentmods.dev/badge/skills/dotoricode/tink-harness/tink-list.svg" alt="Measured on agentmods" 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.00015 | $0.00100 |
| Opus 5 | $0.00008 | $0.00050 |
| Sonnet 5 | $0.00003 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
Tink: 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 7d 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.
What it actually says
Tink List
This is the Codex alias for $tink:list.
- Read
../tink-core/RULES.mdfirst. - Treat this invocation as
$tink:list. - Follow the canonical Tink list behavior.
- Accept legacy
$tink listwording as the same action, but present$tink:listin guidance.
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.
- 7d ago First seen · 14 lines · 15 tokens per session scan A c4b9ffee2d54
Tink: List is a skill published in the GitHub repository dotoricode/tink-harness (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 100 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 skills, from other repositories
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
intuitive-flow
Stable execution/change router after an approved plan, preflight contract, or tiny concrete task. Refactor-shaped work delegates to intuitive-refactor, and durable work runs through staged planning, review, GSD handoff, implementation, cleanup, and verification while keeping plan ledgers and active capsules compact by…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
multica-goal-tracker
Track goal-driven Multica issues. Use when a user creates or maintains Multica issues by pasting a /goal prompt, wants Codex to summarize that goal into a concise issue purpose, append a normalized goal-start comment, record completion evidence from real Multica execution run messages or a supplied session transcript…
intuitive-reduce-entropy
Inspect a repository or plan and rank material simplification candidates. Use repo entropy mode when the cleanup owner is unknown, and plan entropy mode when an idea or plan needs blind spots found before approval. This skill discovers and routes work; it does not implement refactors.