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.
npx skills add Lab2A/metalworks --skill go-no-gogit clone --depth 1 https://github.com/Lab2A/metalworksWrote 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/skills/lab2a/metalworks/go-no-go)<a href="https://agentmods.dev/skills/lab2a/metalworks/go-no-go"><img src="https://agentmods.dev/badge/skills/lab2a/metalworks/go-no-go/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/skills/lab2a/metalworks/go-no-go"><img src="https://agentmods.dev/badge/skills/lab2a/metalworks/go-no-go.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.00124 | $0.00998 |
| Opus 5 | $0.00062 | $0.00499 |
| Sonnet 5 | $0.00025 | $0.00200 |
| Haiku 4.5 | $0.00012 | $0.00100 |
Grade A, and why
go-no-go 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble (run first)
Before any other tool, run the preflight MCP tool (or metalworks preflight on
the CLI). If it reports setup issues or that an update is available, surface that
to the user in one line and help them resolve it (install the missing extra/key,
or pip install -U metalworks) before continuing. Skip only if the user has
already passed preflight this session.
Read the reference; never reverse-engineer the source. The moment you need to know how
metalworks behaves — provider/model resolution, which source/reader runs, config precedence,
an error you hit, or the async run loop — STOP and read docs/operating-metalworks.md
(bundled with this plugin) before opening any file under src/. It is the source of truth;
do not derive behavior from source. (Full docs: https://metalworks.lab2a.ai/docs.) For a
long-running run, poll status with the Monitor tool or a bounded loop — never a blind sleep.
You are giving a founder the honest verdict. The decision itself is computed — demand strength (how many distinct people) measured against landscape saturation (what already exists) — so you are not guessing; you are arguing the computed call with evidence and recording the human's decision. Three lanes, never two: GO, PIVOT (real demand, wrong target), NO-GO.
Steps
-
Get the
report_id. No report yet → run/demand-reportfirst; the verdict stands on the report's clusters and its landscape. -
Call the
assess_from_reportMCP tool with thereport_id(or CLI:metalworks research assess <report_id>). It runs the landscape, then the deterministic gap, and returns anAssessment: adecision, agap(demand strength × landscape saturation), arationale, and — on PIVOT — apivot_target. -
Deliver it like an office-hours partner, honestly:
- Lead with the decision and the one-line gap: "GO — strong demand (47 distinct voices), open landscape" / "PIVOT — real demand but the space is crowded" / "NO-GO — thin demand."
- Argue it with evidence. Resolve the assessment's
EvidenceRefs and show the real quotes behind the demand; name the competitors / existing solutions behind the saturation. - On PIVOT, make the target concrete. Show the
pivot_target— the under-served wedge or segment the report surfaced — and why it's the better bet. PIVOT loops back to ideation with that target. - On NO-GO, don't soften it. Say why plainly; thin demand or a saturated space with no opening is a real answer.
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.
- 9d ago First seen · 66 lines · 124 tokens per session scan A 3f268dcdce5a
go-no-go is a skill published in the GitHub repository Lab2A/metalworks (6 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 998 once invoked, about $0.0006 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…