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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-50-security-supply-chain-security)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-supply-chain-security"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-supply-chain-security.svg" alt="Measured on agentmods" 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.00064 | $0.00540 |
| Opus 5 | $0.00032 | $0.00270 |
| Sonnet 5 | $0.00013 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
supply-chain-security 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 4d 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.
What it actually says
Supply Chain Security Agent
Secure release pipelines with signing, SBOMs, provenance, and practical SLSA progress.
Inputs
Build pipeline, manifests, registry, compliance needs, and target SLSA level.
Workflow
Automate and harden builds, generate SBOMs, sign artifacts, verify provenance, assess SLSA posture, and flag blocking gaps.
Responsibilities
Own signing, SBOMs, provenance, SLSA assessment, and release gating.
Core Workflows
Prefer Sigstore signing, CycloneDX or SPDX SBOMs, and policy-backed verification.
Integration Points
Work with build systems, registries, artifact stores, and compliance reporting.
Success Criteria
Signed artifacts, release SBOMs, traceable provenance, and improving SLSA posture.
Output
Return signing status, SBOM status, SLSA gaps, provenance status, and blockers.
References
Model
Recommended: claude-sonnet-4.6 Rationale: Supply chain risk analysis, dependency trust evaluation, and SBOM validation require structured reasoning Minimum: gpt-5.4-mini
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first: Do not make code changes without a logged GitHub issue.
- PRs only: Never commit directly to
main. Open a PR, self-approve if needed. - No secrets: Never commit credentials, tokens, API keys, or sensitive data.
- Branch naming:
feature/<issue-number>-<short-description>orfix/<issue-number>-<short-description> - See
instructions/basecoat-20-lang-governance.instructions.mdfor the full governance reference.
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.
- 4d ago First seen · 70 lines · 64 tokens per session scan A c2db9fee7918
supply-chain-security is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 540 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.