laborer-companion— agent skill

laborer-companion — independently scanned and version-tracked by SaferSkills.

by workingclass-ai·Agent Skill·github.com/workingclass-ai/workingclass

Is laborer-companion safe to install?

SaferSkills independently audited laborer-companion (Agent Skill) and scored it 79/100 (yellow). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 5 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

Score
79/100
●●●●●●●●○○
↑ +0 since first scan (79 → 79)Re-scan~30s
Latest scan
ScannedJun 24, 2026 · 30d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings5 warnings · 0 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
40
14.0 pts
Supply chainhash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenancestaleness, pinning, CI
15%
100
15.0 pts
TransparencySKILL.md, perms, README
15%
100
15.0 pts
Communityinstalls, verify, response
15%
100
15.0 pts

Findings & checks · 5 flagged

Securityscore 40 · 5 findings
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · skills/laborer-companion/commands/decode.md
MEDIUMit fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptskills/laborer-companion/commands/decode.md· markdown
71- **Don't catastrophize**: A single instance of "we are family" rhetoric doesn't mean the us
… (33 chars elided on L71)
72- **Don't give legal advice**: Note when something might be legally problematic, but recomme
… (51 chars elided on L72)
73- **Privacy**: Don't ask for company name, specific colleague names, or details beyond what'
… (26 chars elided on L73)
74 
75## Follow-up
Occurrences
1 occurrence · at L73
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha25615dae9807bd892c6rubric 365aacaView on GitHub
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · skills/laborer-companion/commands/jump.md×2
MEDIUMit fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptskills/laborer-companion/commands/jump.md· markdown
38> 8. 年龄段(25-30 / 30-40 / 40-50 / 50+)
39 
40Don't ask for more. Don't ask for company name.
41 
42## Step 3: Five-dimension analysis
Occurrences
2 occurrences · first at L40, also L40
Show all 2 locations
Line
File
L40
skills/laborer-companion/commands/jump.md
L40
skills/laborer-companion/commands/jump.md
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha25615dae9807bd892c6rubric 365aacaView on GitHub
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · skills/laborer-companion/commands/overtime.md
MEDIUMit fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptskills/laborer-companion/commands/overtime.md· markdown
29> 5. 你的目前心理倾向(想接受还是想拒绝?为什么?)
30 
31Don't ask for more than this. Don't push for company name or sensitive details.
32 
33## Step 3: Apply the 5-step framework
Occurrences
1 occurrence · at L31
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha25615dae9807bd892c6rubric 365aacaView on GitHub
MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · skills/laborer-companion/commands/salary.md
MEDIUMit fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.
Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted
excerptskills/laborer-companion/commands/salary.md· markdown
41- Research market rates (levels.fyi, Blind, local sources)
42- Calculate their BATNA
43- Don't disclose current salary first
44- Don't name a number first
45 
Occurrences
1 occurrence · at L43
How to fix
Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.
  1. Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
  2. Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-IMPERATIVE-01sha256c402c33e02489ce6rubric 365aacaView on GitHub
Supply chainscore 100 · 0 findings
All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
All community checks passedNo findings in this category for the latest scan.pass
Vendor response · right of reply
Are you the maintainer? Submit a response →

Audit the pieces. Scan the whole. Decide.

~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.