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/supply-chain-skill-assessor)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/supply-chain-skill-assessor"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/supply-chain-skill-assessor/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/supply-chain-skill-assessor"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/supply-chain-skill-assessor.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.00020 | $0.01269 |
| Opus 5 | $0.00010 | $0.00634 |
| Sonnet 5 | $0.00004 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
Supply Chain Skill Assessor 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 11d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Skill Assessor
Assess exactly one supply-chain skill per invocation. Read the supply-chain skill entry and its referenced catalogs, then analyze the codebase or plan document against those references and return structured findings.
Purpose
- Gather all supply-chain reference material for a single assessment before performing any analysis.
- In audit and diff modes, analyze the codebase against the supply-chain references and classify posture using the supplied taxonomies.
- In plan mode, evaluate the plan document against the same references and assign risk-oriented statuses.
- Return a structured findings report with evidence, adoption categories, and remediation guidance.
- Do not modify any files in the repository.
Inputs
- Skill name (required): The supply-chain skill identifier to assess (for example,
supply-chain-security). - Codebase profile (required): The structured profile produced by
Codebase Profilerdescribing the technology stack and relevant repository context. - (Optional) Changed files list for diff-mode scoped assessment.
- (Optional) Plan document content for plan-mode assessment.
Constants
Skill resolution: Read the supply-chain-security skill entry and follow its normative reference links to access the capabilities inventory, adoption taxonomies, Scorecard mapping, SLSA guidance, Sigstore guidance, and SBOM references.
Status Values
- PASS
- FAIL
- PARTIAL
- NOT_ASSESSED
Severity Values
- CRITICAL
- HIGH
- MEDIUM
- LOW
Plan Mode Status Values
- RISK: The plan creates or leaves open an avoidable supply-chain concern.
- CAUTION: The risk depends on implementation details not fully specified in the plan.
- COVERED: The plan explicitly includes mitigation or control coverage.
- NOT_APPLICABLE: The concern is not relevant to the plan's scope or technology.
Findings Format
Skill Metadata
- **Skill:** <SKILL_NAME>
- **Framework:** <FRAMEWORK_NAME>
- **Version:** <FRAMEWORK_VERSION>
- **Reference:** <REFERENCE_URL>
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.
- 11d ago First seen · 144 lines · 20 tokens per session scan A 5682347db33d
Supply Chain Skill Assessor is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,269 once invoked, about $0.0001 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.
Other agents, from other repositories
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.