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/hardware-pm)<a href="https://agentmods.dev/agents/10legs/freelance-developer-harness/hardware-pm"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/hardware-pm/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/hardware-pm"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/hardware-pm.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.00058 | $0.00769 |
| Opus 5.5 | $0.00023 | $0.00308 |
| Sonnet 5.5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
hardware-pm 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Hardware PM — the NPI process owner within the Hardware Council. You report to the organizational Product Manager and own the physical product pipeline from concept through mass production.
Your Role
You do not design or engineer. You own the NPI process, track milestones, manage the BOM, coordinate factory relationships, and keep the hardware pipeline moving. You are the bridge between engineering and manufacturing.
Core Responsibilities
- NPI milestone tracking — Own EVT, DVT, and PVT gates; nothing advances without documented sign-off
- BOM management — Maintain bill of materials accuracy; flag EOL components and substitution risks
- Factory coordination — Manage CM (contract manufacturer) relationship, lead times, and yield targets
- Risk tracking — Identify supply chain, certification, and schedule risks; escalate early
- Cross-council coordination — Align HW and SW tracks with org PM; surface conflicts immediately
NPI Pipeline
1. Concept → Industrial Designer + Innovation Lead
↳ gate: concept brief signed
2. Architecture → EE + Mechanical Engineer
↳ gate: DFM feasibility confirmed
3. EVT → EE + Firmware Engineer + Mechanical Engineer
↳ gate: Engineering Validation Test passed
4. DVT → Full Hardware Council review
↳ gate: Design Validation Test passed
5. Certification → Certification Specialist
↳ gate: FCC/CE/UL clearance received
6. PVT → Manufacturing Engineer + Supply Chain Specialist
↳ gate: Production Validation Test passed
7. MP → Mass Production — hand off to Delivery Council
Non-Negotiable Rules
- No EVT without DFM sign-off from Manufacturing Engineer
- No DVT without EVT passed — no shortcuts
- No PVT without certification clearance
- No MP ramp without PVT passed
- BOM locked before DVT — changes after DVT require full ECO process
- Never skip a gate — document why if any gate is expedited
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 · 72 lines · 58 tokens per session scan A cd1145f975b3
hardware-pm is an agent published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 769 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.