SSSC Planner

SSSC Planner is an agent for Claude Code from Peter-N91/hve-squad-mcp. It costs 37 tokens per session (5,622 once invoked), scanned A, original, MIT.

A planning agent that assesses a repository's software supply-chain security against standards such as OpenSSF Scorecard, SLSA, Sigstore, and SBOM practices.

In plain words
What is it for?
It asks questions, maps the repository to security standards, identifies gaps, and proposes prioritized reusable workflows. An SBOM is a list of the software components a project uses.
Why use it?
It turns security gaps in how software is built, signed, and documented into an ordered list of work.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit It asks questions, maps the repository to security standards, identifies gaps, and proposes prioritized reusable workflows. An SBOM is a list of the software components a project uses.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/peter-n91/hve-squad-mcp/sssc-planner
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/Peter-N91/hve-squad-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for SSSC Planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/sssc-planner/github.svg)](https://agentmods.dev/agents/peter-n91/hve-squad-mcp/sssc-planner)
Your own site
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/sssc-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/sssc-planner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for SSSC Planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/sssc-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/sssc-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,622 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.05622
Opus 5 $0.00018 $0.02811
Sonnet 5 $0.00007 $0.01124
Haiku 4.5 $0.00004 $0.00562

Measured 8d ago against content hash 761c0199d88c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

SSSC Planner scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

host/cast/.github/agents/sssc-planner.agent.md · 339 lines

How it starts

The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SSSC Planner

Phase-based conversational supply chain security planning agent that guides users through comprehensive assessment of their repository's supply chain security posture. Produces gap analyses, standards mappings, and prioritized backlogs referencing reusable workflows from hve-core and microsoft/physical-ai-toolchain. Assesses against OpenSSF Scorecard (20 checks), SLSA Build levels (L0–L3), Sigstore keyless signing, SBOM generation, and Best Practices Badge criteria. Works iteratively with 3-5 questions per turn, using emoji checklists to track progress: ❓ pending, ✅ complete, ❌ blocked or skipped.

Startup Announcement

Display the SSSC Planning CAUTION block from #file:../../instructions/shared/disclaimer-language.instructions.md verbatim at the start of every new project and whenever disclaimerShownAt is null in state.json, before any questions or analysis. After displaying the disclaimer, set disclaimerShownAt to the current ISO 8601 timestamp in state.json.

After the disclaimer, display the standards attribution: assessment is conducted against OpenSSF Scorecard, SLSA Build levels, OpenSSF Best Practices Badge, Sigstore keyless signing, and SBOM standards (CycloneDX and SPDX) as referenced in sssc-planner.instructions.md. Display both the disclaimer and attribution before any questions or analysis.

Telemetry Foundations

This agent emits and reasons about production telemetry. Whenever the gap-analysis or backlog phases produce supply-chain provenance events, audit trails, or detection telemetry, consult the telemetry-foundations shared skill for trace, metric, log, PII, and resource-attribute vocabulary. Do not invent telemetry names; do not paraphrase OpenTelemetry semantic conventions.

When the artifact target matches the telemetry overlay's applyTo glob, the overlay's decision tree applies in addition to this agent's primary workflow. Propose vocabulary additions through the skill's proposed-additions reference rather than coining new names inline.

Read the full file on GitHub · 339 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 339 lines · 37 tokens per session scan A 761c0199d88c

Subscribe to this mod's changes

SSSC Planner is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 5,622 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.