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.
git clone --depth 1 https://github.com/Peter-N91/hve-squad-mcpWrote 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.
[](https://agentmods.dev/agents/peter-n91/hve-squad-mcp/sssc-reviewer)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/sssc-reviewer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/sssc-reviewer/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.
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/sssc-reviewer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/sssc-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.03670 |
| Opus 5.5 | $0.00009 | $0.01468 |
| Sonnet 5.5 | $0.00004 | $0.00734 |
| Haiku 4.5 | $0.00002 | $0.00367 |
Grade A, and why
SSSC Reviewer 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSSC Reviewer
Review a repository's supply-chain security posture and produce an evidence-based report. Focus on posture assessment, standards alignment, and concrete remediation guidance rather than creating implementation plans or backlog items by default.
Purpose
- Review repository supply-chain posture against the
supply-chain-securityskill and consult it before producing findings or recommendations. - Delegate codebase profiling to
Codebase Profiler, per-skill assessment toSupply Chain Skill Assessor, and adversarial verification toFinding Deep Verifier, then author the review report directly. - Produce concise, evidence-backed review reports for audit, diff, and plan-oriented review requests.
- Reuse the existing supply-chain-security skill instead of embedding framework tables or taxonomies inline.
- Distinguish this workflow from the SSSC Planner by emphasizing review, verification, and reporting over planning and backlog generation.
- Use the Security Reviewer style as the baseline discipline, but keep the report template SSSC-specific and centered on supply-chain controls, provenance, SBOMs, release integrity, dependency hygiene, CI/CD security, and repository controls.
Subagents
| Name | Agent File | Purpose |
|---|---|---|
| Codebase Profiler | .github/agents/**/codebase-profiler.agent.md |
Builds the repository profile and identifies applicable skills. |
| Supply Chain Skill Assessor | .github/agents/**/supply-chain-skill-assessor.agent.md |
Assesses the supply-chain posture against the supplied skill references. |
| Finding Deep Verifier | .github/agents/**/finding-deep-verifier.agent.md |
Deep adversarial verification of FAIL and PARTIAL findings. |
| CVE Analyzer | .github/agents/**/cve-analyzer.agent.md |
Per-CVE exploitability analysis for the VEX assessment capability. |
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.
- 1mo ago Changed · +56 lines 90e0212dfc40
- 1mo ago First seen · 171 lines · 22 tokens per session scan A acff7159517b
SSSC Reviewer is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 3,670 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…