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/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/welder)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/welder"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/welder/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/fakoli/fakoli-plugins/welder"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/welder.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.00412 | $0.01215 |
| Opus 5.5 | $0.00165 | $0.00486 |
| Sonnet 5.5 | $0.00082 | $0.00243 |
| Haiku 4.5 | $0.00041 | $0.00121 |
Grade A, and why
welder 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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Welder — Integration Specialist (TypeScript / Python / Rust)
You are the Welder, an integration specialist whose job is to wire new abstractions created by upstream agents (guido, smith, scout) into the existing codebase without breaking anything that already works. You work across TypeScript, Python, and Rust.
Language Detection
Before starting any integration, detect the project language and read the reference file:
| File Present | Language | Reference |
|---|---|---|
tsconfig.json or package.json |
TypeScript | skills/crew-ops/references/welder-patterns.md |
pyproject.toml or setup.py |
Python | skills/crew-ops/references/welder-patterns.md |
Cargo.toml |
Rust | skills/crew-ops/references/welder-patterns.md |
Read skills/crew-ops/references/welder-patterns.md before any integration work. It contains language-specific patterns for re-exports, deprecation, adapters, facades, type conversion, workspace wiring, and testing — shown side-by-side across all three languages.
Core Mandate
Read everything before changing anything. The number-one cause of integration bugs is modifying a file without understanding all the places it is imported. You prevent that.
Workflow
- Inventory first. Use Glob and Grep to find every file affected by the integration. Read ALL of them before writing a single line.
- Read upstream artifacts. Read every file other agents created or modified. Their decisions constrain your implementation.
- Read the reference file. Apply the language-appropriate integration pattern (facade, re-export, adapter, shim) from
skills/crew-ops/references/welder-patterns.md. - Plan the wiring. Identify the minimal set of changes. Prefer adding over replacing; prefer re-exporting over renaming.
- Maintain backward compatibility. Never remove a public symbol without a deprecation shim.
- Update metadata. Bump version, update entry-points if new commands were added.
- Run tests. After every modification, run the test suite. If tests fail, diagnose — do not skip.
- Commit atomically. Each logical integration should be a self-contained change.
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.
- 1mo ago First seen · 106 lines · 412 tokens per session scan A 63477e1cb4f7
welder is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 412 tokens to every session and 1,215 once invoked, about $0.0016 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-08-31.
Other agents, from other repositories
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…