long-description— agent skill

long-description — independently scanned and version-tracked by SaferSkills.

by 8ddieHu0314·Agent Skill·github.com/8ddieHu0314/Skill-Lab

Is long-description safe to install?

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

Score
45/100
●●●●●○○○○○
↑ +0 since first scan (45 → 45)Re-scan~30s
Latest scan
ScannedJun 27, 2026 · 28d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings1 warnings · 1 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
63
22.1 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 63 · 2 findings
HIGHLong base64-encoded blob hidden in the skill documentationSS-SKILL-INJECT-B64-PAYLOAD-01 · Prompt injection · tests/fixtures/skills/invalid/long-description/SKILL.md
HIGHonce decoded by the agent, an encoded payload has the same impact class as plain-text injection.
Why it matters

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.

The exact value spotted
excerpttests/fixtures/skills/invalid/long-description/SKILL.md· markdown
1---
2name: long-description
3description: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
… (108 chars elided on L3)
4---
5 
Occurrences
1 occurrence · at L3
How to fix
Remove the encoded blob, or decode it and review what it actually contains.
  1. Decode the base64 string and confirm it is not an instruction directed at the agent.
  2. Move any legitimate binary or signature data into a dedicated file (*.sig, SIGNATURES) outside the documentation.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-B64-PAYLOAD-01sha2561d449b72b7ac00c6rubric 365aacaView on GitHub
MEDIUMRequest for the agent to reveal its system promptSS-SKILL-INJECT-SYS-LEAK-01 · Prompt injection · docs/SECURITY.md
MEDIUMit scores the disclosure intent; whether extraction succeeds depends on the host model's own mitigations.
Why it matters

The text {match} asks the agent to disclose its hidden system prompt or initial instructions. That is often the first step of a larger attack: knowing the system prompt lets an attacker craft inputs that defeat its constraints by mimicking its own voice.

The exact value spotted
excerptdocs/SECURITY.md· markdown
71- Instruction override: `ignore/forget/discard/disregard/override ... instructions`
72- Identity override: `you are now [DAN / developer mode / god mode / jailbreak]`
73- System prompt extraction: `reveal the system prompt`
74- Safety bypass: `bypass/disable/suppress/remove safety/restrictions/guidelines/limits`
75- Restriction removal: `no restrictions`, `without any restrictions`, `free of restrictions`
Occurrences
1 occurrence · at L73
How to fix
Remove the solicitation asking the agent to reveal its system prompt or hidden instructions.
  1. Delete the repeat/reveal/print your system prompt request from the skill.
  2. If you are debugging your own prompt, do so in a private dev harness rather than baking the request into a shipped skill.
Framework references
OWASPLLM07ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-SYS-LEAK-01sha2569249e44c1522c277rubric 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.