thrunt-new-workspace — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited thrunt-new-workspace (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 4 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 4 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<context> Flags:
--name (required) — Workspace name--repos — Comma-separated repo paths or names. If omitted, interactive selection from child git repos in cwd--path — Target directory. Defaults to ~/thrunt-workspaces/<name>--strategy — worktree (default, lightweight) or clone (fully independent)--branch — Branch to checkout. Defaults to workspace/<name>--auto — Skip interactive questions, use defaults</context>
<objective> Create a physical workspace directory containing copies of specified git repos (as worktrees or clones) with an independent .planning/ directory for isolated THRUNT sessions.
Use cases:
.planning/Creates:
<path>/WORKSPACE.md — workspace manifest<path>/.planning/ — independent planning directory<path>/<repo>/ — git worktree or clone for each specified repoAfter this command: cd into the workspace and run /hunt-new-program to initialize THRUNT. </objective>
<execution_context> @.github/thrunt-god/workflows/new-workspace.md @.github/thrunt-god/references/ui-brand.md </execution_context>
<process> Execute the new-workspace workflow from @.github/thrunt-god/workflows/new-workspace.md end-to-end. Preserve all workflow gates (validation, approvals, commits, routing). </process>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.