thrunt-manager — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited thrunt-manager (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.
<objective> Single-terminal command center for managing a milestone or hunt campaign. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work. In hunt mode that means shape/plan/run; in THRUNT utility mode it means management, audit, and workspace flows.
Designed for power users who want to parallelize work across phases from one terminal: shape or discuss a phase while another plans or runs in the background.
Creates/Updates:
.planning/STATE.md, MISSION.md, HUNTMAP.md, and phase directories for status.After: User exits when done managing, or all phases complete and the appropriate publish/verify lifecycle is suggested. </objective>
<execution_context> @.github/thrunt-god/workflows/manager.md @.github/thrunt-god/references/ui-brand.md </execution_context>
<context> No arguments required. Requires MISSION.md, HUNTMAP.md, and STATE.md.
Project context, phase list, dependencies, recommendations, and workflow mode are resolved inside the workflow using thrunt-tools.cjs init manager. No upfront context loading needed. </context>
<process> Execute the manager workflow from @.github/thrunt-god/workflows/manager.md end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete. </process>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.