Loading the registry…
Sweep a BatonDeck board's finished tickets into Chronicle decision records — both tiers. Reads a durable project-memory cursor, takes the window of task.completed / task.reopened / task.requeued / task.moved-into-DONE events since it, pulls each ticket's composed context over MCP, pipes the batch through the repo's deterministic emitter (which writes docs/chronicle/adr/NNNN-*.md, stamps superseded_by, and regenerates the topics/index mechanical regions), ingests the resulting pages with ingest_chronicle_page (sourcePath filled), raises ONE docs PR for the batch, and advances the cursor only after the ingest succeeded AND the PR is raised — so a sweep that dies mid-flight is re-derived on the next run instead of losing tickets. Forge (GitHub) review threads are best-effort enrichment that never blocks a sweep, and every record declares which evidence it actually had. Invoked by the plugin's /batondeck:chronicle command.
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.
2 critical findings reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/tech-sumit/batondeck-plugin, 52 findings
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'tech-sumit/batondeck-plugin (batondeck-chronicle)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'tech-sumit/batondeck-plugin (batondeck-chronicle)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.
v2.0.11
34 findings · 9.8s
v0.3.74
9 findings · 1.5s
v0.1.0
2 findings · 4.4s
v0.1.0
5 findings · 4.4s
v0.1.0
0 findings · 9.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
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 16, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: complete | 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.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 50 findings above stand exactly as their scanners reported them, at full severity.