clinical-reports— agent skill

clinical-reports — independently scanned and version-tracked by SaferSkills.

by rbr7·Agent Skill·github.com/rbr7/MedClawMini

Is clinical-reports safe to install?

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

Score
92/100
●●●●●●●●●
↑ +0 since first scan (92 → 92)Re-scan~30s
Latest scan
ScannedJun 28, 2026 · 28d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings2 warnings · 0 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
76
26.6 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 · 2 flagged

Securityscore 76 · 2 findings
MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · skills/clinical-reports/references/peer_review_standards.md×2
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/clinical-reports/references/peer_review_standards.md· markdown
29 
30**Maintain confidentiality:**
31- Do not share manuscript content
32- Do not use information for personal advantage
33- Do not involve others without editor permission
Occurrences
2 occurrences · first at L31, also L497
Show all 2 locations
Line
File
L31
skills/clinical-reports/references/peer_review_standards.md
L497
skills/clinical-reports/references/peer_review_standards.md
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-01sha25660e40095f47950ccrubric 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.