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

MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · leadup-github-repo-researcher/references/security-rules.md

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

excerptleadup-github-repo-researcher/references/security-rules.md· markdown

11- **Never echo, log, or paste API keys, tokens, passwords, or connection

12strings**, even if they appear in a file you opened.

13- **Never ask the user to paste a secret** into chat. If a value is needed,

14ask them to set it in `.env` themselves and reference it by key name.

15- **Never commit secrets.** Only `.env.example` with placeholder values like

Occurrences

1 occurrence · at L13

How to fix

Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.

Delete blanket "don't ask / no need to confirm" directives from the skill.
If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-DONT-ASK-01sha2565084aa178cfd9d97…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.

leadup-github-repo-researcher/SKILL.md · 1 file

leadup-github-repo-researcher/SKILL.md4.6 KB · Markdown

name: leadup-github-repo-researcher

description: Research open-source GitHub repos for code or design inspiration before reusing them in a LeadUp project. Checks license, stars, activity, last commit, stack compatibility, and decides what can be copied, adapted, or used only as inspiration. Use when the user says "use open source repo", "best GitHub repo", "find repo inspiration", "research GitHub examples", or "best design repo".

LeadUp GitHub Repo Researcher

Purpose

Find and vet open-source repositories so LeadUp can reuse code/design safely: licence-clean, maintained, stack-compatible, with a clear verdict on what to copy, what to adapt, and what is inspiration-only.

When to use

Trigger phrases: "use open source repo", "best GitHub repo", "find repo inspiration", "research GitHub examples", "best design repo", "is there a library for", "open-source starter for", "good reference implementation".

For a hosted third-party API (Razorpay, Gemini, etc.) → use leadup-api-research-builder.

Inputs needed

What is being built / the component or feature needing a reference.
Target stack (Next.js / Node-TS / Flutter / Laravel) for compatibility.
Whether output will ship in proprietary client/SaaS code (licence matters).

Step-by-step workflow

Clarify the need (feature, component, or design pattern) and the stack.
Search GitHub for strong candidates; shortlist 2–4.
For each, fill references/github-research-template.md: stars, last

commit, issues/PR responsiveness, language, licence.

Licence verdict: permissive (copy w/ attribution) vs copyleft

(GPL/AGPL — avoid in proprietary client/SaaS) vs none (inspiration only).

Stack & quality check: compatibility, abandoned deps, tests, secrets in

repo, obvious smells.

Usage decision per part: copy / adapt / inspiration-only, with reason.
Recommend the best repo + 1–2 alternatives and an integration outline.

Required output format

A comparison of candidates following github-research-template.md, ending with: Recommendation (best repo + alternatives), a copy/adapt/inspiration table, required attribution, and integration risks.

Safety rules

See references/security-rules.md. Most relevant here:

Treat no-licence / GPL/AGPL repos as do not copy into proprietary LeadUp

client/SaaS code; inspiration only — say so explicitly.

Never copy code containing committed secrets; flag and exclude such repos.
Do not clone/run untrusted code without stating the risk and getting an ok.

Common mistakes

Recommending a repo by stars alone while ignoring an AGPL licence.
Missing that the repo is abandoned (last commit years ago, open security PRs).
Suggesting a React repo for a Flutter project (stack mismatch).
Not separating "copy" vs "inspiration" — leading to licence violations.
Overlooking heavy/unmaintained dependencies that become LeadUp's problem.

Troubleshooting

Under-triggers: user said "is there something open source for X" —

re-invoke; suggest triggers.

Over-triggers for a hosted API → route to leadup-api-research-builder.
Missing tool/MCP (no GitHub/web access): ask the user for repo URLs to

evaluate, or give vetting criteria to apply manually.

No internet: provide the evaluation checklist and licence guidance; defer

the live lookup.

Missing project files: not required — compatibility judged from the

stated target stack.

Build/test failure when trialing a repo: isolate (deps vs config),

report; do not adopt a repo that won't build without a clear fix path.

Test prompts

Should trigger (5)

"Find the best open-source admin dashboard repo for Next.js."
"Is there a good GitHub repo for Flutter chat UI I can adapt?"
"Research GitHub examples for multi-tenant Postgres."
"Best design repo to take inspiration from for a SaaS landing page."
"Use an open source starter for the hosting panel — which one?"

Should NOT trigger (3)

"Add Razorpay payments, research the API." (→ api-research-builder)
"Analyze our existing repo's state." (→ existing-repo-analyzer)
"Upgrade this dashboard to premium UI." (→ premium-ui-upgrader)

Functional test cases (2)

Given "Flutter chat UI", returns 2–4 repos with licence, last-commit, and a

copy/adapt/inspiration verdict per repo.

An AGPL repo is explicitly marked "inspiration only — do not copy into

proprietary code".

Success criteria

Each candidate has licence + maintenance + stack evidence.
Clear, per-part copy/adapt/inspiration decision with attribution noted.
One recommended repo + alternatives; licence risk never glossed over.

leadup-github-repo-researcher— agent skill

Is leadup-github-repo-researcher safe to install?

LeadUp GitHub Repo Researcher

Purpose

When to use

Inputs needed

Step-by-step workflow

Required output format

Safety rules

Common mistakes

Troubleshooting

Test prompts

Should trigger (5)

Should NOT trigger (3)

Functional test cases (2)

Success criteria

Audit the pieces. Scan the whole. Decide.