tsk

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.

Security

Grade A, and why

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

.claude-plugin/marketplace.json · 27 lines

What it actually says

{
  "name": "tsk",
  "owner": {
    "name": "tsk-tsk contributors"
  },
  "metadata": {
    "description": "Claude Code skills for tsk-tsk: sandboxed AI agent task delegation"
  },
  "plugins": [
    {
      "name": "tsk-help",
      "description": "Teaches Claude core tsk commands for delegating tasks to AI agents in sandboxed containers.",
      "source": "./skills/tsk-help"
    },
    {
      "name": "tsk-config",
      "description": "Guides users through configuring tsk Docker container images for their project.",
      "source": "./skills/tsk-config"
    },
    {
      "name": "tsk-add",
      "description": "Helps queue a development task from the current conversation using tsk add.",
      "source": "./skills/tsk-add"
    }
  ]
}

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.

Related

Other plugins, from other repositories