Routes any product, engineering, or software development lifecycle (SDLC/PDLC) activity to Forge. Invoke this skill whenever the user describes work that involves the product development process — across any phase: discovery, definition, planning, execution, review, handoff, release, or reporting. This includes: building or shipping features, fixing bugs, writing PRDs, breaking down stories, estimating, prioritizing, reviewing PRs, security audits, vulnerability assessments, release readiness checks, deployment gates, test planning and strategy, refactoring, mapping or documenting system architecture across the codebase, reconstructing an architecture estate or building an architecture atlas, or any similar SDLC activity. ALSO invoke when the current user request directly targets a tracked work item key matching "PROJ-123" / "BUG-42" / any "<UPPERCASE>-<digits>" id. Do NOT invoke for pure coding requests ("write a function", "refactor this file", "add a test") or continuation of already-scoped execution, even when a tracked key appears only in earlier conversation context. Do NOT invoke for git operations, file editing, applying already-scoped review feedback, resolving merge conflicts, publishing an existing change, or general Q&A unrelated to a project.
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.
4 critical findings reported by cisco-skill-scanner, agent-audit-kit. 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 -- 'shiptoday/forge-plugin-claude-mp (forge-autopilot)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'shiptoday/forge-plugin-claude-mp (forge-autopilot)' ~/.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
20 findings · 11.0s
v0.3.74
4 findings · 1.7s
v0.1.0
0 findings · 5.4s
v0.1.0
0 findings · 5.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
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 · 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 ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-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 24 findings across every scanner that examined this package. None of the 4 findings rated critical by their scanner were dismissed.
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.
8 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/plugins/forge-shiptoday/hooks/must-display.cjs, /repo/plugins/forge-shiptoday/hooks/session-state.cjs · reported by cisco-skill-scanner
5 MANIFEST_MISSING_LICENSE
Files: /repo/plugins/forge-shiptoday/skills/forge-workflow/SKILL.md, /repo/plugins/forge-shiptoday/skills/forge-autopilot/SKILL.md, /repo/plugins/forge-shiptoday/skills/forge-feedback/SKILL.md and 2 more · reported by cisco-skill-scanner
2 LOW_ANALYZABILITY
Files: /repo, /repo/plugins/forge-shiptoday · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/plugins/forge-shiptoday/SKILL.md · reported by cisco-skill-scanner
2 YARA_prompt_injection_generic
Files: /repo/plugins/forge-shiptoday/hooks/stop-observer.cjs · reported by cisco-skill-scanner
1 AAK-MARKETPLACE-001
Files: .claude-plugin/marketplace.json · reported by agent-audit-kit
1 AAK-MCP-001
Files: plugins/forge-shiptoday/.mcp.json · reported by agent-audit-kit
1 AAK-MCP-ATTEST-001
Files: plugins/forge-shiptoday/.mcp.json · reported by agent-audit-kit
1 AAK-MCP-AUTH-PATHTRAVERSAL-001
Files: plugins/forge-shiptoday/hooks/session-state.cjs · reported by agent-audit-kit
1 MANIFEST_DESCRIPTION_TOO_LONG
Files: /repo/plugins/forge-shiptoday/skills/forge-autopilot/SKILL.md · reported by cisco-skill-scanner
Critical path traversal and prompt injection risks, with potential for data egress.
The artifact contains critical path traversal vulnerabilities in authentication logic within `session-state.cjs`, which could allow unauthorized access to files. Multiple instances of generic prompt injection patterns are present in `stop-observer.cjs`. Additionally, the artifact exhibits high-severity file system access capabilities in `must-display.cjs` and `session-state.cjs`, indicating potential for data egress.
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.