thrunt-workstreams — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited thrunt-workstreams (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.
Manage parallel workstreams for concurrent milestone work.
/thrunt-workstreams [subcommand] [args]
| Command | Description |
|---|---|
list | List all workstreams with status |
create <name> | Create a new workstream |
status <name> | Detailed status for one workstream |
switch <name> | Set active workstream |
progress | Progress summary across all workstreams |
complete <name> | Archive a completed workstream |
resume <name> | Resume work in a workstream |
Parse the user's input to determine which workstream operation to perform. If no subcommand given, default to list.
Run: node "$THRUNT_TOOLS" workstream list --raw --cwd "$CWD" Display the workstreams in a table format showing name, status, current phase, and progress.
Run: node "$THRUNT_TOOLS" workstream create <name> --raw --cwd "$CWD" After creation, display the new workstream path and suggest next steps:
/hunt-new-program --ws <name> to set up the milestoneRun: node "$THRUNT_TOOLS" workstream status <name> --raw --cwd "$CWD" Display detailed phase breakdown and state information.
Run: node "$THRUNT_TOOLS" workstream set <name> --raw --cwd "$CWD" Also set THRUNT_WORKSTREAM env var for the current session.
Run: node "$THRUNT_TOOLS" workstream progress --raw --cwd "$CWD" Display a progress overview across all workstreams.
Run: node "$THRUNT_TOOLS" workstream complete <name> --raw --cwd "$CWD" Archive the workstream to milestones/.
Set the workstream as active and suggest /thrunt-resume-work --ws <name>.
Format the JSON output from thrunt-tools into a human-readable display. Include the ${THRUNT_WS} flag in any routing suggestions.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.