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 AndrewDongminYoo/cc-agents-kit --skill setup-trunkgit clone --depth 1 https://github.com/AndrewDongminYoo/cc-agents-kitWrote 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/andrewdongminyoo/cc-agents-kit/setup-trunk)<a href="https://agentmods.dev/skills/andrewdongminyoo/cc-agents-kit/setup-trunk"><img src="https://agentmods.dev/badge/skills/andrewdongminyoo/cc-agents-kit/setup-trunk.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.00044 | $0.03717 |
| Opus 5 | $0.00022 | $0.01858 |
| Sonnet 5 | $0.00009 | $0.00743 |
| Haiku 4.5 | $0.00004 | $0.00372 |
Grade C, and why
setup-trunk scanned grade C with 1 finding 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 6d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- trunk-ignore-all(trunk/ignore-unknown-linter) --> How it starts
The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Trunk
Overview
Trunk.io is a meta-linter and git hook manager.
Its core principle is "hold-the-line": existing violations are acknowledged and ignored initially, but new violations on changed files are blocked.
This lets teams adopt linting incrementally without a big-bang cleanup.
This skill covers first-time integration and configuration. Running trunk day to day is a different job — trunk check / trunk fmt at milestones, cache corruption, aligning trunk-pinned linter versions with the workspace, vulnerability triage — and is out of scope here.
Initialization Flow
1. Inspect the repository before selecting linters
Do not start from a memorized linter bundle. First inspect the repository's manifests and lockfiles, existing CI workflows, declared package scripts, language and generated-file layout, and any existing linter configuration. Use that evidence to identify tools the project already runs, file types that actually exist, and checks CI already owns.
git ls-files | grep -E '(^|/)(package.json|pubspec.yaml|pyproject.toml|Cargo.toml|go.mod|Podfile)$'
git ls-files '.github/**'
git ls-files | grep -Ei '(^|/)([^/]*(eslint|prettier|ruff|markdownlint|shellcheck)[^/]*)$'
Read the files found, including scripts in manifests and the commands used by CI, before proposing lint.enabled.
Enable a linter only when a repository artifact or an explicit user requirement supports it; do not infer that mobile, web, infrastructure, and documentation checks all belong in the same repository.
2. Run trunk init
trunk init
The wizard prompts for:
- Account connection (optional for local-only use)
- Linter auto-detection based on files in the repo
- Git hooks setup (built-in actions)
- Initial full-repo scan to snapshot existing violations
For open-source repos where you contribute a PR to someone else's codebase and don't want to commit trunk config:
trunk init # then: trunk config hide
trunk config hide adds .trunk/ to .gitignore, keeping the config local.
Alternatively, trunk init --single-player-mode does both in one step (verified in trunk init --help: "initialize trunk with a gitignored config, run 'trunk config share' to undo").
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.
- 6d ago First seen · 395 lines · 44 tokens per session scan C b0d356a43a69
setup-trunk is a skill published in the GitHub repository AndrewDongminYoo/cc-agents-kit (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 3,717 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.
detect-task
Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.
loop-bb-pr
A command that prepares a repeating check for a Bitbucket pull request. A pull request is a request to review and merge code changes into a project.
take-task
A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.