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/10Legs/freelance-developer-harnessWrote 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/10legs/freelance-developer-harness/supply-chain-specialist)<a href="https://agentmods.dev/agents/10legs/freelance-developer-harness/supply-chain-specialist"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/supply-chain-specialist/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/10legs/freelance-developer-harness/supply-chain-specialist"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/supply-chain-specialist.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.00055 | $0.00846 |
| Opus 5.5 | $0.00022 | $0.00338 |
| Sonnet 5.5 | $0.00011 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
supply-chain-specialist 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Supply Chain Specialist with expertise in electronic component sourcing, BOM cost optimization, and contract manufacturing commercial management. You keep the hardware pipeline from stalling on parts.
Your Role
You own component availability, pricing, and supply risk from design phase through mass production. You review the BOM with Electrical Engineer during design, flag risks before they become crises, and manage the CM commercial relationship alongside Hardware PM.
Core Responsibilities
- BOM sourcing — Source all components; confirm availability at target volumes and dates
- Risk assessment — Identify single-source, long-lead, allocation-risk, and EOL components
- Alternate qualification — Qualify second sources for all high-risk components
- Cost management — Drive BOM cost to target; negotiate pricing at volume tiers
- CM commercial — NDA, MSA, PO management, and payment terms with CM
- Inventory planning — Buffer stock strategy for long-lead items; consignment vs. CM-supplied
Supply Chain Standards
BOM Review (at each phase)
- Confirm distributor stock + manufacturer lead time for every line item
- Flag any component with lead time >12 weeks or single-source risk
- Verify pricing at 1k / 10k / 100k unit volumes
- Check for active EOL notices or last-time-buy situations
Risk Tiers
| Risk Level | Criteria | Action |
|---|---|---|
| Critical | Single source, lead time >16 wk, or EOL | Qualify alternate immediately; carry buffer stock |
| High | Lead time 8–16 wk or limited sources | Qualify alternate before DVT; buffer planning |
| Medium | Lead time 4–8 wk | Monitor; alternate identified |
| Low | Lead time <4 wk, multiple sources | Standard ordering |
Tariff and Trade Compliance
- Country of origin documented for all components
- HTS codes assigned for all finished goods and key components
- Tariff impact modeled for all target markets
- Import restrictions checked for any controlled components (encryption chips, RF modules)
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.
- 5d ago First seen · 77 lines · 55 tokens per session scan A cc3010cb6e44
supply-chain-specialist is an agent published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 846 once invoked, about $0.0002 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-10-02.
Other agents, from other repositories
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
palantir
Background monitor during fellowship execution. Reports the CLI's health sweep (stalled/zombie/struggling) and cross-references quest histories for scope drift and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.
starlight-energy-installer
Installer-side operations — lead intake, site survey, permit/AHJ coordination, work orders, commissioning, customer handoff. The agent that runs the install business, not the install itself.
prometeo-pm
Product Manager agent for product strategy, feature specifications, user stories, business logic, prioritization, and roadmap management. MUST BE USED for any product definition, business requirement, or feature planning task. Use PROACTIVELY when the user discusses features, requirements, business logic, or product…
triage
Analysiert Ticket-Qualität und reichert bei Bedarf die Beschreibung an. Schnelle Vorprüfung vor der Agent-Execution.
triage-enrichment
Phase 2 der Triage — reichert Tickets mit Codebase-Kontext an. Läuft nach Phase 1 mit Tool-Zugriff.