Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dtormoen/tsk-tsk/plugin install tsk-configWrote 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/dtormoen/tsk-tsk/tsk-config)<a href="https://agentmods.dev/skills/dtormoen/tsk-tsk/tsk-config"><img src="https://agentmods.dev/badge/skills/dtormoen/tsk-tsk/tsk-config/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.
<a href="https://agentmods.dev/skills/dtormoen/tsk-tsk/tsk-config"><img src="https://agentmods.dev/badge/skills/dtormoen/tsk-tsk/tsk-config.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.02852 |
| Opus 5.5 | $0.00018 | $0.01141 |
| Sonnet 5.5 | $0.00009 | $0.00570 |
| Haiku 4.5 | $0.00005 | $0.00285 |
Grade B, and why
tsk-config scanned grade B with 2 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# Enable passwordless sudo inside containers Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Every container includes: Ubuntu 25.10, git, git-lfs, build-essential, curl, jq, just, ripgrep, sudo, Python 3, uv, podman (for DIND), and an `agent` user (UID 1000). How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tsk Docker Configuration Guide
You are helping a user configure tsk Docker container images for their project. Follow these steps in order.
Step 1: Gather Project Information
Detect the project's technology stack by checking for these files in the project root. These are tsk's built-in stacks with auto-detection — custom stacks for any language can be defined via stack_config in tsk.toml (covered in Step 5).
| File | Stack |
|---|---|
Cargo.toml |
rust |
go.mod |
go |
package.json |
node |
pyproject.toml, requirements.txt, setup.py |
python |
pom.xml, build.gradle, build.gradle.kts |
java |
rockspec, .luacheckrc, init.lua |
lua |
| None of the above | default |
Also determine the project name from the current directory name.
Tell the user what you detected and ask them to confirm or override. If their stack isn't listed above, let them know they can define a custom stack.
Step 2: Check for Deprecated Dockerfiles
Check if .tsk/dockerfiles/ exists. If it does, warn the user:
Deprecated:
tskno longer supports filesystem-based dockerfiles in.tsk/dockerfiles/. Docker customization is now done viasetupfields intsk.toml. This guide will help you migrate to the new format.
List any files found in .tsk/dockerfiles/ and note their contents — you will use them to populate the new config.
Step 3: Choose Configuration Location
Ask the user where to put the configuration:
- Project-level (
.tsk/tsk.toml): Checked into version control, shared with the team. Best for project-specific dependencies that all contributors need. - User-level (
~/.config/tsk/tsk.toml): Personal settings, not shared. Best for machine-specific paths, personal preferences, or settings across multiple projects.
If the user picks user-level, config goes under [project.<project-name>] in ~/.config/tsk/tsk.toml. If project-level, config goes at the top level of .tsk/tsk.toml.
Step 4: View the Current Docker Build
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.
- 1mo ago First seen · 324 lines · 46 tokens per session scan B afad85288ecc
tsk-config is a skill published in the GitHub repository dtormoen/tsk-tsk (171 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 2,852 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
loom-docker
Docker and container expertise.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
loom-kustomize
Kubernetes-native configuration management with Kustomize.
docker-management
Manage and debug Docker containers, images, volumes, networks, Compose stacks, and Dockerfile performance/safety.
container-operations
Build, inspect, debug, and validate Docker or Podman images, containers, networks, volumes, and Compose stacks.
loom-karpenter
Kubernetes node autoscaling and cost optimization with Karpenter.