CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 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 · 1 flagged

Securityscore 88 · 1 finding

MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · README.md

MEDIUM — it 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

excerptREADME.md· markdown

840- Never commit `update_hr_contacts.py` to Git (contains real recruiter names/LinkedIn URLs)

841- Keep your Gmail App Password secure

842- Don't share your Excel tracker if it contains private data

843

844## Acknowledgements

Occurrences

1 occurrence · at L842

How to fix

Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.

Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-IMPERATIVE-01sha256d9839cdc44f5a183…rubric 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

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/open-hot-jobs/SKILL.md · 1 file

.claude/skills/open-hot-jobs/SKILL.md1.2 KB · Markdown

name: open-hot-jobs

description: This skill should be used when the user wants to open hot job listings in Chrome. Triggers on phrases like "open hot jobs", "open [category] hot jobs in chrome", "open all backend jobs", "open jobs in browser", "open [category] jobs chrome".

Open Hot Jobs in Chrome

Opens job URLs from daily_hot_jobs.json in Chrome tabs.

Categories (exact keys in JSON)

Senior Java
Backend Java
Product Owner
Assistant Project Manager
Tech Lead / Lead Developer
AI / GenAI Engineer

Steps

Read daily_hot_jobs.json.
Identify which category the user wants (or all categories if unspecified).
Extract the url field from each job in current_jobs[category].
Open all URLs at once using: start chrome "url1" "url2" ...
Confirm how many tabs were opened and for which category.

Notes

If no category is specified, ask the user which one (or confirm if they want all).
If a category has no jobs ([]), tell the user it's empty.
Use Comet browser (Perplexity): "$LOCALAPPDATA/Perplexity/Comet/Application/comet.exe" --new-window "url1" "url2" ... &
Always open in a new window using --new-window.

open-hot-jobs— agent skill

Is open-hot-jobs safe to install?

Open Hot Jobs in Chrome

Categories (exact keys in JSON)

Steps

Notes

Audit the pieces. Scan the whole. Decide.