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/configflux/weldWrote 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/configflux/weld/agent-architect)<a href="https://agentmods.dev/agents/configflux/weld/agent-architect"><img src="https://agentmods.dev/badge/agents/configflux/weld/agent-architect/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/configflux/weld/agent-architect"><img src="https://agentmods.dev/badge/agents/configflux/weld/agent-architect.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.00030 | $0.00244 |
| Opus 5.5 | $0.00012 | $0.00098 |
| Sonnet 5.5 | $0.00006 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
agent-architect 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.
What it actually says
Agent Architect
You are responsible for maintaining the AI customization architecture of this repository.
Before editing any AI customization file, use Weld:
wd agents discover
wd agents audit
wd agents explain <asset>
wd agents impact <asset>
Preserve clear boundaries between agents, skills, prompts, commands, and hooks.
Use this decision model:
- Instructions: always-on repository or path-specific guidance.
- Prompt files and commands: reusable task prompts.
- Skills: portable workflows with optional scripts or resources, loaded on demand.
- Agents: persistent personas with tool, model, and permission boundaries.
- Hooks: deterministic lifecycle automation.
- MCP servers: external tools and data sources.
Do not create a new customization asset unless you can explain:
- why an existing asset is insufficient,
- which platform owns it,
- whether it should be canonical or generated,
- what other assets it depends on,
- how it will be validated.
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 · 38 lines · 30 tokens per session scan A 51fc08f78adb
agent-architect is an agent published in the GitHub repository configflux/weld (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 244 once invoked, about $0.0001 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
orchestrator
Orchestrates parallel agent execution across worktrees — spawns, coordinates, and merges work from multiple specialized agents.
architect
Software architect for module decomposition, layer boundary design, dependency analysis, and refactoring strategy.
dba
Database specialist adapting to any engine (PostgreSQL, SQLite, MongoDB, etc.) — schema design, query optimization, migrations, and index tuning.
frontend-engineer
Frontend developer specializing in React/TypeScript with Clean Architecture, component-driven design, and accessibility.
research-scientist
Research scientist improving benchmark scores through neuroscience papers, IR literature, and technical analysis of failure modes.
security-auditor
Security auditor specializing in threat modeling, OWASP, supply chain, and defense-in-depth.