one-by-one— agent skill

one-by-one — independently scanned and version-tracked by SaferSkills.

by Warnes-Innovations·Agent Skill·github.com/Warnes-Innovations/oboe-mcp

Is one-by-one safe to install?

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

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

Securityscore 38 · 3 findings
HIGH"Ignore previous instructions" command embedded in the skillSS-SKILL-INJECT-IGNORE-01 · Prompt injection · .github/oboe_sessions/session_20260411_120000.json×2
HIGHwhen it fires on hostile content the impact is full system-prompt override.
Why it matters

The text {match} is the classic direct prompt-injection phrasing. Placed in a skill body that the agent reads as trusted instructions, it tries to make the agent abandon its prior rules and follow whatever comes next — a full system-prompt override.

The exact value spotted
excerpt.github/oboe_sessions/session_20260411_120000.json· json
95"title": "Risk classification taxonomy",
96"category": "Design",
97"description": "How should we classify the severity/risk of findings?\n\n**Proposed taxonomy
… (102 chars elided on L97)
98"urgency": 3,
99"importance": 4,
Occurrences
2 occurrences · first at L97, also L217
Show all 2 locations
Line
File
L97
.github/oboe_sessions/session_20260411_120000.json
L217
.github/oboe_sessions/session_20260411_120000.json
How to fix
Remove the override phrase, or rephrase the passage so it does not instruct the agent to discard its rules.
  1. Delete the ignore/disregard/forget … previous instructions sentence.
  2. If this is jailbreak-research or tutorial content, move the example into a clearly fenced, non-instruction block and label it as a quoted sample.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-IGNORE-01sha2562e4221a7f996a729rubric 365aacaView on GitHub
MEDIUMRequest for the agent to reveal its system promptSS-SKILL-INJECT-SYS-LEAK-01 · Prompt injection · .github/oboe_sessions/session_20260411_120000.json
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
excerpt.github/oboe_sessions/session_20260411_120000.json· json
215"title": "Detection rules: initial rule set scope",
216"category": "Design",
217"description": "What detection patterns should be in the initial rule set?\n\n**Proposed ini
… (102 chars elided on L217)
218"urgency": 3,
219"importance": 5,
Occurrences
1 occurrence · at L217
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-01sha2560a16e35c7a0d4be0rubric 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.