Use when the user wants to authenticate with or log in to the ArchAstro developer platform, or when the CLI reports an authentication error. Trigger phrases include "authenticate archastro", "archastro auth login", "log in to archastro", "archastro not authenticated", "archastro auth status", "sign in to archastro".
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.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'archastro/archastro (auth)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'archastro/archastro (auth)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
46 findings · 8.6s
v0.3.74
3 findings · 3.0s
v0.1.0
0 findings · 3.8s
v0.1.0
15 findings · 3.8s
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.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 7.9s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged39 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
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 64 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 48 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
1 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: opt.nerlo-rules.nerlo-install-run-bundled-artifact · Files: /repo/.github/workflows/installer-smoke-test.yml · reported by nerlo-install-instruction
The model could have called any of these a false positive and did not.
12 HIDDEN_DATA_FILE
Files: /repo/.claude-plugins/archastro/skills/build-skill/SKILL.md, /repo/.claude-plugins/archastro/skills/author-agent/SKILL.md, /repo/.claude-plugins/archastro/skills/chat/SKILL.md and 9 more · reported by cisco-skill-scanner
2 AAK-MARKETPLACE-001
Files: .claude-plugin/marketplace.json, .agents/plugins/marketplace.json · reported by agent-audit-kit
1 AAK-SECRET-004
Files: scripts/check_plugin_repo.py · reported by agent-audit-kit
47 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: opt.nerlo-rules.nerlo-install-fetch-raw-then-run, opt.nerlo-rules.nerlo-install-pipe-to-shell, PIPELINE_TAINT_FLOW and 2 more · Files: /repo/.claude-plugins/archastro/commands/install.md, /repo/README.md, /repo/plugins/archastro/skills/install/SKILL.md and 21 more · reported by nerlo-install-instruction, cisco-skill-scanner
1 The model gave no reason we were willing to publish, and a verdict without one is not usable evidence.
Rules: HIDDEN_DATA_FILE · Files: /repo/.claude-plugins/archastro/commands/impersonate.md · reported by cisco-skill-scanner
Critical: Shell execution, credential access, and data flow risks.
The artifact contains instructions that fetch and execute raw scripts from external sources and pipe content directly to a shell, indicating potential for arbitrary shell execution in installation files. High-severity findings also point to credential access within `scripts/check_plugin_repo.py`. Additionally, pipeline taint flow findings suggest potential for data manipulation or code injection in several markdown files. These capabilities are present in installation instructions and plugin configuration files.
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.