Loading the registry…
Take exactly one eligible story issue from the backlog through the full development cycle — select it, branch a worktree, implement the acceptance criteria, run the repository's verify commands, open a pull request, wait for checks, get a review from the configured roster and answer it, then label the pull request for GitHub to auto merge, close the issue and clean up. Use this whenever the user asks to "work the backlog", "take the next issue", "do the next story", "pick up the next ticket", or runs the backlog loop; it is also what the `issue-worker` agent invokes on every iteration of `backlog:run-backlog`. Everything repository-specific comes from `.claude/backlog.json`. Skip this when the user names a specific issue to explore rather than to land, or when they want the backlog bootstrapped rather than worked — that is `backlog:setup-backlog`.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
9 critical findings reported by cisco-skill-scanner, agent-audit-kit, 4 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'z5labs/devex (next-issue)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'z5labs/devex (next-issue)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
2 findings · 1.4s
v2.0.11
102 findings · 45.7s
v0.3.74
5 findings · 73.5s
v0.1.0
0 findings · 159.2s
v0.1.0
10 findings · 159.2s
vv0.3.2
Incomplete run
0 findings · 1.0s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 22, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 119 findings across every scanner that examined this package. 5 of 9 findings rated critical by their scanner were among the dismissals.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
35 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: YARA_command_injection_generic, FILE_MAGIC_MISMATCH, PDF_STRUCTURAL_THREAT and 6 more · Files: /repo/daggerverse/qemu/tests/artifacts.go, /repo/daggerverse/skill-gen/skill/skill_test.go, /repo/daggerverse/bruno/tests/fixtures/data/tenants.txt and 11 more · reported by cisco-skill-scanner
5 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: opt.nerlo-rules.nerlo-install-shell-inline-command, opt.nerlo-rules.nerlo-install-run-bundled-artifact · Files: /repo/docs/dagger-internals/caching-and-evaluation.md, /repo/daggerverse/skill-gen/skill/testdata/golden/README.md · reported by nerlo-install-instruction
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
30 MANIFEST_MISSING_LICENSE
Files: /repo/plugins/backlog/skills/run-backlog/SKILL.md, /repo/plugins/backlog/skills/next-issue/SKILL.md, /repo/plugins/backlog/skills/setup-backlog/SKILL.md and 27 more · reported by cisco-skill-scanner
25 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/plugins/SKILL.md, /repo/daggerverse/SKILL.md and 22 more · reported by cisco-skill-scanner
5 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/daggerverse/bruno/README.md, /repo/daggerverse/java/README.md, /repo/daggerverse/opentofu/README.md and 2 more · reported by nerlo-install-instruction
3 PIPELINE_TAINT_FLOW
Files: /repo/daggerverse/flash/probers.go · reported by cisco-skill-scanner
3 YARA_command_injection_generic
Files: /repo/daggerverse/tesseract/batch_selfcheck.go · reported by cisco-skill-scanner
Artifact presents critical command injection and system manipulation risks.
The artifact contains critical findings for potential command injection in `/repo/daggerverse/tesseract/batch_selfcheck.go`, indicating a risk of shell execution. High severity findings also point to system manipulation capabilities in `/repo/daggerverse/z5labs/build.go` and pipeline taint flow in `/repo/daggerverse/flash/probers.go`. Additionally, the artifact has a critical finding related to skill functionality in `plugins/daggerverse/skills/plan-dagger-module/SKILL.md` and high severity findings concerning marketplace configuration and trust settings.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
2 AAK-MARKETPLACE-001
Files: .claude-plugin/marketplace.json · reported by agent-audit-kit
2 EXCESSIVE_FILE_COUNT
Files: /repo/daggerverse/., /repo/. · reported by cisco-skill-scanner
2 YARA_system_manipulation_generic
Files: /repo/daggerverse/z5labs/build.go · reported by cisco-skill-scanner
1 AAK-SKILL-003
Files: plugins/daggerverse/skills/plan-dagger-module/SKILL.md · reported by agent-audit-kit
1 AAK-TRUST-004
Files: .claude/settings.json · reported by agent-audit-kit
1 AAK-TRUST-006
Files: .claude/settings.json · reported by agent-audit-kit
1 hooks-no-pretooluse
Files: settings.json · reported by agentshield
1 LOW_ANALYZABILITY
Files: /repo/daggerverse/pdf · reported by cisco-skill-scanner
1 MANIFEST_DESCRIPTION_TOO_LONG
Files: /repo/plugins/backlog/skills/run-backlog/SKILL.md · reported by cisco-skill-scanner
1 permissions-no-deny-list
Files: settings.json · reported by agentshield